I get the basic concepts, and combining that with the specifics of how MC works, is the following summary correct to be as clear as possible?
I don't think so.
Normally you have MC, the library and the data (audio files) on 1 computer.
You can move the data to a NAS or any PC in the network.
This won’t make a difference compared with an all local setup except you have to create a share on the ‘NAS’.
What happens if more than 1 PC access the share.
Each PC has its own library, each PC uses the same files on the share
Anytime any PC changes something ( e.g. a tag) this change will be stored in the local library but MC will also write the tag in the data.
It will probably lock the file when doing so.
Each PC can modify or delete the files.
Now you can make the share read only for all but yourself.
I expect MC to generate an error message each time a user changes something because MC expects write access.
This is in essence what happens when using file sharing.
Maybe if you put all other PC’s in party mode you won’t have this problems.
I never tried the MC server but I do expect it to work like any other client/server environment.
The serve contains the data and the library.
The clients don’t access data and library directly but send commands to the server.
The server processes the request and modify library and data accordingly.
In this scenario all PC’s have access to the same library.
If you make a e.g. a playlist, it is available for all.
Again all probably have the right to modify.
If the server is implemented well this won’t generate access conflicts.