Hey jorn!
Attached is the basic skeleton (client-side only) of gupnp-av i
could think of. You would immediately note that the pxoxy objects are
not derived from the GUPnP device and service proxy objects and the
reason for that is that AVControl point would not have any control
over the creation of the the proxy objects and hence can not create
these AV specific proxies. So either we make GUPnPControlPoint more
extensible or we have the av-specific proxies to "contain" (instead of
derive) the GUPnP proxy objects.
One easy way to make control point extensible that comes to mind
straight-away, is to make the static methods of control point that
creates the proxies when the description document is ready, virtual.
What do you think?
-- Regards, Zeeshan Ali
-- To unsubscribe send a mail to gupnp+unsubscribe\@o-hand.com
This archive was generated by hypermail 2.1.8 : Sat Jul 28 2007 - 09:00:06 EDT