search for: buildplaylist

...don't have one huge function > > I agree some part of the code could be included in a single > function to avoid code duplication. Make a function dispatcher > to point to each function who give the corresponding HTTP header > for each format. I suspect we could define a /admin/buildplaylist and pass the type as an arg, allowing for multiple types and multiple streams to be listed. So for example /admin/playlist?mount=/stream&type=pls karl.

Hi Karl, > While I think most of this is fine, I think in the fserve part (where > the checks to see if there is a playlist file in webroot), they all > seem to follow the same pattern so that would tend to indicate a > function to reduce duplication. > > At the moment I'm wondering whether these responses could be > automatically generated from xslt files? like xspf is.