The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: Re: Homevision Help


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

Re: xPLMediaNet and Playlists


  • Subject: Re: xPLMediaNet and Playlists
  • From: "Mal Lansell" <mlansell@xxxxxxxxxxxxxx>
  • Date: Wed, 16 Mar 2005 20:09:39 -0000



--- In ukha_xpl@xxxxxxx, "Tony Tofts" <tony@x> wrote:
> Hi all,
>
> Need some advise and/or suggestions please.
>
> I'm trying to remove the reliance on a database from xplmedianet
as far as
> possible
>

My feeling is that playlists should be treated as a media type, just
like an mpg or an mp3.  After all, you can browse and play playlists
in the same way as individual files.  The fact that they actually
point to other media files is irrelevant to the way the user
interacts with them - handling a playlist (from a user perspective)
is really no different to dealing with the chapters in a DVD movie.

As such, any module that requires the database - which to my mind
should just be the media selection modules (browse, web interface
etc), should use the same method to select a playlist as any other
file.

The only other part of the system that needs access to the database
(if I understand correctly) would be the core, which would need to
access it to obtain file locations - either to send in xPL commands,
or for the serving of files to devices that require that.

Client modules, sources and transcoders should not need to access
the database at all.

Mal












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

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.