[Playlist] [rfc] Nested playlists (and playlist chains) again

[Lucas Gonze]

Linking to external XSPF files is very much good practice.  Handling 
this kind of powerful functionality gracefully is just the kind of value 
that libSpiff can enable.

Embedding playlists in order to put a whole database into one file is 
very much not good practice.  That's on the other side of the dividing 
line between a catalog and a playlist.  And I agree that this gets us 
into a hell, even if we decide to enable it.


Sebastian Pipping wrote:
> The more I think about this nested playlists will get
> us into hell A if we go that way and hell B if we go
> the other. I think the driver behind this being requested
> over and over (including me) is the desire to put
> a whole database into one single file. The question is
> how far that can and should go: When we want to
> store several playlists with e.g. their own <title>s
> things start to get really messy. Should we push that
> into extensions? Should we put a whole <playlist> into
> an extension tag? Will parsers be able to deal with
> this in a reasonable use/cost ratio? I don't think so.
> 
> 
> So maybe the best thing to do is decide to not support
> nested playlists. XSPFv0/1 was not designed for this
> and if a tree structure is needed it can still be handle
> one layer above XSPF - in the application logic.
> 
> Nevertheless we should think about linking to external
> XSPF files from within XSPF and define what's good practice
> and what's not. Or is that clear already?
> 
> Please throw any thoughts on me now! If you feel your thoughts
> are already made for the FAQ entry [1] please go ahead
> and point us to it.
> 
> 
> 
> Sebastian
> 
> 
> [1] http://wiki.xiph.org/index.php/XSPF_FAQ#Are_nested_playlists_possible.3F
> 
> 
> _______________________________________________
> Playlist mailing list
> Playlist at lists.musicbrainz.org
> http://lists.musicbrainz.org/mailman/listinfo/playlist
> 
>