Re: [gupnp] gupnp-av

Hi again!

> > Hmm.. I am not surprised of this thought since I didn't imagine the
> > wrappers to be any thick but i was thinking of providing objects like:
> >
> > * GUPnPAVConnection (or call it a GUPnPAVPair or whatever) that would
> > ease the process of connecting and controlling (the playback between)
> > media servers and renderers.
> >
> > * GUPnPAVContolPoint (again :)) that would only ease the process of
> > finding compatible pairs of mediaservers and renderers, create
> > GUPnPAVConnection object for each compatible pair and signal the
> > application about it's availability and unavailability.
>
> That would be nice, but the problem here is in the notion of compatible
> pairs of servers and renderers. Not all media on one server may be
> playable by the same renderer.

   I must admit i didn't think of that but would having separate
GUPnPAVConnection (or is GUPnPAVPair a better name) for each
compatible mediatype be a bad idea? An abstraction for 'Browse' can be
provided as a method of this object but it would only list the
contents that are of the mediatype this pair object represents. What
do you say?

> > Hmm.. I don't see much use of this. Why can't the app just use
> > gupnp control point for searching for particular device/service and
> > call Browse method on MediaServers?
>
> Yeap, agree.

  Glad we agree. :)

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