Hi Daniel, I now see that you really want to play again something that has been played before. This has never been a need before (at least not one that we identified) so there is basically nothing done in that area. There's no reason to it besides this.
It would be possible for a request source (such as playlist or queue) to remember the past track URIs and give a way to recall them. There are design questions, for example how to make things uniform for requests and playlists, but that would be a really interesting project. Just do it! :) Doing it at a higher level (for all sources and operators) doesn't seem like a good idea, though, but I don't even see what it would bring anyway. You're talking of a feature regarding the scheduling of requests, it should be addressed at a level where requests are processed; once you get a stream from a request, there's no way to get back to the request. Cheers, -- David ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
