On 9/8/2011 23:23, Max Kellermann wrote: > On 2011/09/09 08:00, Christ Schlacta<aarc...@gmail.com> wrote: >> I've been looking forward to being able to maintain one central MPD >> database for a long time now. keeping it in mysql will hopefully make >> that possible. simply update from any daemon, and tell the rest of the >> daemons to reload the database and instawin. > Not only that; I'm planning to write a database backend that will run > as a MPD client to another MPD server. > > Use case: have one big fat file server, running one central MPD that > keeps its database up to date; weak satellite MPD servers mount the > file system (via NFS, SMB) and don't need to maintain their own > database, they just forward all requests to the one on the file > server. > > The central MPD can be just a dummy, with a "null" output. > > Max that's not horrible, so long as the performance is up to snuff. I envision a similar experience with mysql, where only one has write access and everyone else has read. If both work, which will perform better?
------------------------------------------------------------------------------ Why Cloud-Based Security and Archiving Make Sense Osterman Research conducted this study that outlines how and why cloud computing security and archiving is rapidly being adopted across the IT space for its ease of implementation, lower cost, and increased reliability. Learn more. http://www.accelacomm.com/jaw/sfnl/114/51425301/ _______________________________________________ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
