On 2009/10/26 16:35, Steffen 'stefreak' Neubauer <stefr...@stefreak.de> wrote: > But if MPD will not accept a change to it's protocol and/or it's source > i think a fork is not the best way. Then i would design an own > protocol.
You're free to do so. Good luck with your fork. > - most protocols are Client/Server architecture based. (mpd too, but a > p2p mode could easily be integrated.) What is the disadvantage of a client/server architecture? Why does that contradict with "p2p mode"? > - most protocols do more than i want - like listing files and folders > or user+password authentication and writing to the file system (ftp, > nfs, smb). Don't implement what you don't need. All of the protocols you mentioned allow anonymous access. NFS doesn't have authentication (at least v3; NFSv4 has extensions for authentication). However NFSv4 with file listings and tags in "virtual" file attributes sounds like a clever solution... there might be more clever solutions involving HTTP or WebDAV. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
