Re: [gupnp] general event notification

Hey!

On Tue, 2007-07-31 at 19:32 +0300, Zeeshan Ali wrote:
> Yo!
>
> On 7/31/07, Jorn Baayen <jorn@openedhand.com> wrote:
> > On Tue, 2007-07-31 at 18:58 +0300, Zeeshan Ali wrote:
> > > Hey Jorn!
> > > I just found out that GUPnPServiceProxy provides the ability to
> > > track changes in individual state variables but not all variables in
> > > general (Which is quite the opposite of what UPnP itself provides). I
> > > am not saying the former is a bad thing but IMHO we *must* provide the
> > > later as well. Agreed?
> >
> > Why do you need this?
>
> For one thing, to avoid writing the following code:
>
> ================== code snippet ============
> GUPnPServiceIntrospection *introspection;
>
> introspection =
> gupnp_service_info_get_introspection (
> GUPNP_SERVICE_INFO (proxy),
> NULL);
>
> if (introspection) {
> const GList *variable_node;
>
> variable_node =
> gupnp_service_introspection_list_state_variables (
> introspection);
>
> for (; variable_node; variable_node = variable_node->next) {
> GUPnPServiceStateVariableInfo *variable;
>
> variable = (GUPnPServiceStateVariableInfo *)
> variable_node->data;
>
> gupnp_service_proxy_add_notify (
> proxy,
> variable->name,
> variable->type,
> on_state_variable_changed,
> NULL);
> }
>
> g_object_unref (introspection);
> }
> ==============================================

But what does is it give you? I don't see how knowing that "some state
variable changed" is useful, especially when querying for state variable
values is not possible .. (QueryStateVariable is deprecated)

Thanks,

Jorn

>
> But i now that i think about it, this is needed by generic clients
> only and they would be using and depending on introspection anyway.
>

--
To unsubscribe send a mail to gupnp+unsubscribe\@o-hand.com