Re: Some thoughts on xplmedianet and how to implement

["Malcolm Lansell" <mlansell@xxxxxxxxxxxxxx>]

----- Original Message -----
From: "Tony Tofts" <tony@xxxxxxx>
To: <ukha_xpl@xxxxxxx>
Sent: Friday, March 11, 2005 10:50 AM
Subject: RE: [ukha_xpl] Some thoughts on xplmedianet and how to implement


>
> Hi Mal,
>
> Ok, I understand now
>
> I was making the assumption of 1 genre per artist/album
>
> As the database is being slightly restructured anyway, I'll be able to
add
> a
> genre xref to artists/albums without too much trouble.
>
> To simplify how stuff is handled I'll probably replace 'Genres' with
> 'Genre
> Artist', 'Genre Album' and 'Genre Track'.
>
> With regards to not using the database, that's correct - all modules
are
> optional.
>
> Though as things stand you'd need a 'directory browse' source module.
>
> Though in this mode obviously no selections other than browsing would
be
> available (though you can use both!)
>
> I may well produce such a module, and remove the current xplrionet
browse
> that actually uses the database.
>
> I guess we can add an extra item to the xpl-cmnd schema for your web
> interface:
>
> File=c:\an artist\an album\a track.mp3 to queue a track by filename
> (though
> how do we handle the 128byte limit on the path/filename length?)
>

This issue keeps coming up - how to represent files in an xPL message.
Since 128 bytes is well short of the MAX_PATH used in Windows, we simply
have no choice but to split the filename up.

How about using an array value (like the groups and filters)
Each element stores a piece of path, so the message would read

file="c:"
file="an artist"
file="an album"
file="a track.mp3"

The "\" characters are implied.
URLs can be passed using this system too.

Regards

Mal
(BTW, I'll reply to the other message later - I need to take some time to
think about it)











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