Quote:
Originally Posted by James  There is however always a problem with central storage. If the central server is not available the features that require it will not work. So I think some kind of synchronisation would be better.
/James |
I beleive the way that the MythTV project has done it is to use Master/Slave dbs, where your master acts as a publisher to each of the slaves/clients, so you get a situation where settings are basically cached locally, but always available through the master when anything changes or an updated configuration is loaded.
This also allows you to de-centralize storage, but have all media...etc accessible from everywhere...you'd just have to make sure to write some smart code that can work on/offline as needed, and handle a good deal of special events...