The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: xPLRioNet is Dead?, Long live xPLMediaNet? - xPLRioNet users please read!


  • Subject: RE: xPLRioNet is Dead?, Long live xPLMediaNet? - xPLRioNet users please read!
  • From: "Tony Tofts" <tony@xxxxxxxxxx>
  • Date: Mon, 7 Mar 2005 11:11:15 -0000


Hi Mal,

> I too was about to suggest a replacement for audio.basic - my
> app currently uses something called av.basic, to cover video
> related controls, but it sounds like the same thing that
> media.basic would be (and media.basic is probably a better
> name anyway).  Perhaps we should come up with a list of all
> the commands we will need?

Yes, good idea. Most of the commands I need are the ones already in
xplrionet, but they need expanding a bit.

> As for your plans for xplMediaNet - I'm fine with the idea of
> a core module handling streams of data for those applications
> that need it, but I think all control and status
> communication between modules should be handled through xPL
> messages, rather than some xPLMediaNet specific channel -

The stuff passing thru the core will mainly be:

A) xpl (it will act mainly as an intelligent hub, diverting traffic only to
the destinations, thereby reducing the xpl load on the individual modules)

B) shared service port policing (e.g. modules wishing to use nfs/ftp ports
etc)

C) database activity (as this is inappropriate for xpl, in my view)

D) handling requests for resources like streams (so a stream can be shared)

E.g.

a rio playing a track: the rio module would open/play/stream the track
itself (it wouldn't pull/push thru the core module)

A rio playing a shoutcast stream: the rio module would request the stream,
the core passes this on to a shoutcast module, and links the 2 together.

xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.