Re: [RFC] [PATCH 0/2] Use of GAsyncResult



Hi Victor,

haven't looked at your patches in detail but I guess using GAsync API for things 
like metadata() or resolve() is ok, however I would be more interested in knowing 
how this would work for async methods that provide more than one result per 
call (browse, search, query) as for those I am not sure how the GAsync API would 
fit, do you plan on trying with any of those?

Iago

On Sun, 11 Apr 2010 19:56:46 +0200, Víctor Manuel Jáquez Leal
<vjaquez igalia com> wrote:
> These patch set is a proof of concept of using the gio async calls
> instead of the custom async methods with custom closure structures.
> 
> The metadatasource.resolve_async method is implemented and the vala
> bindings are updated to reflect this new method and gio dependency.
> 
> In order to complete the implementation these commits will need also
> an implementation (fake-metadata) and a test programa
> (async-test.vala), which will follow this thread.
> 
> Víctor Manuel Jáquez Leal (2):
>   [core] resolve_async implementation
>   [vala] update GI and vapi files for async methods support
> 
>  bindings/vala/grilo-0.1.vapi           |    2 +
>  bindings/vala/grilo-0.1/grilo-0.1.deps |    1 +
>  bindings/vala/grilo-0.1/grilo-0.1.gi   |   28 +++++++++
>  configure.ac                           |    3 +-
>  src/Makefile.am                        |    2 +-
>  src/grl-metadata-source.c              |  105 ++++++++++++++++++++++++++++++++
>  src/grl-metadata-source.h              |   17 +++++
>  7 files changed, 156 insertions(+), 2 deletions(-)
>  create mode 100644 bindings/vala/grilo-0.1/grilo-0.1.deps
> 
> _______________________________________________
> grilo-list mailing list
> grilo-list gnome org
> http://mail.gnome.org/mailman/listinfo/grilo-list


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]