[no subject]

An mvp playing a movie: the mvp module would handle everything as per
playing music on the rio

The part the core plays is the xpl master hub (or switch is more
appropriate
term),  policing shared service ports (nfs, dhcp, tftpd - where either a
shared utility module or a device module will handle the function or a
combination of both depending on the requirements for booting the device).
The core will also handle the xpl music menus, which will be totally
independent of the device's own menu's, and database activity between the
database and devices/modules.

> For example, VideoLan doesn't require a
> data-serving application (it can stream from a network
> share), and therefore wouldn't need to use the core module.

In theory this is no different to streaming music on a rio (from the
streaming point of view). It's just that the rio has other requirements
(like access to the database, nfs).

I'm not intending to make xplmedianet a distributed system across multiple
pc's though, so in the case of videolan it would be xpl control only.
Though
videolan can supposedly (I say supposedly as I've had nothing but grief
with
it) act as a source for the mvp, so a source module for it (and videolan
could be on another pc) would be good - acting pretty much like shoutcast
source module.

i.e. mvp module requests a videolan source from the core, the core tells
the
videolan module which then connects to videolan (somewhere) and provides a
stream back to the mvp? This videolan source module could communicate with
videolan either thru the network in some way (if appropriate) or a videolan
xpl connector at the videolan end.

BTW, in theory xplrionet can now play DVD's, some TV card's etc as well as
divx

Regards
Tony



xPL Links: http://www.xplproject.org.uk http://www.xplhal.com http://www.xpl.myby.co.uk
To Post a Message: ukha_xpl@xxxxxxx
To Subscribe:  ukha_xpl-subscribe@xxxxxxx
To Unsubscribe:  ukha_xpl-unsubscribe@xxxxxxx