Re: [gupnp] gupnp-av

Hey!

> Hmm, I see no clear distinction between client and server classes in
> your design?

    Because there were no server classes in it. :)

>Also, will we really need the "Info" classes - I doubt
> there is any "info" that would (sensibly) be available for query from
> both client and server sides?

   Hm.. I am not so sure either, what i sent you was just a rough
picture that came to my mind when i gave it the first thought.

> I rather envisioned something simpler: A set of classes for implementing
> all the different AV services, and a set of classes for controlling
> them: all taking the relevant Service or ServiceProxy objects as
> constructor arguments. We shouldn't need any control point or device
> wrappers (devices merely contain services).

  If we remove the info classes/interfaces and control point from that
diagram, this is what we get. Also, Instead of providing a control
point, we can provide search target macros for each standard AV
device/service.

> Let's see how it goes with the present setup, we can always add these
> virtual methods if necessary. It won't change the API.

  Yup! Please do let me know when you start working on this. :)

-- 
Regards,
Zeeshan Ali
FSF member#5124
--
To unsubscribe send a mail to gupnp+unsubscribe\@o-hand.com