>> Kind of, except it doesn't need UPnD or DLNA, just a new command
>> "download <file>". I had sent a sample patch that provided this command
>> a long time ago. My implementation was purposefully naive, so that it
>> could be used to download any file from the `music' subdirectories (and
>> `playlist', tho this part is not needed any more now that we have
>> listplaylistinfo), which I abused in my MPC.el client to also download
>> files like "<dir>/cover.jpg".
> Why in the hell would anyone want their music player to become a
> network filesystem protocol? I hope this never comes to fruition and
Thanks for bashing my implementation (which I didn't write to submit it
for inclusion, but because I needed to solve an actual problem).
Now, what do you think about my feature request (which can be
implemented in many different ways)?
Stefan
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Musicpd-dev-team mailing list
Musicpd-dev-team@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
