Just use a database and store it on the server. Then point all MC installations to that database. Unfortunately, the issue is that only one at a time (not big deal) and MC doesn't store all settings in the database...many have to be configured for each computer and user instance.
Ummm... you just highlighted all the advantages over your solution, in your solution
lol. How can you "do" anything? You can't really set ratings, create playlists, set sorts on lists, create view schemes, etc? Can you? It's a good way for keeping your MC info static.
Yup, and as you indicate above, there is no advantage to your method (which I use incidently
), apart from having no cache lag time.
At the end of the day, the only reason the Library Server can't be used is due the the caching issue. If that was removed, I cant see any real advantage to the shared library workaround.
C.