by shagmasterk » Sun Jul 25, 2021 5:42 pm
I was excited when I read about MMS today (yes, I am behind), because it seemed like the reason it was created was to allow access to a shared library from "client" devices. That's a great idea! It would be like at work, where there is a server running the database, and all the workstations access and manipulate the database, and changes made from any workstation are almost immediately updated to all other workstations.
- Ideally the workstations or clients, whatever you call them, could be other Windows or mobile devices.
- If ultimately MMS becomes part of the MM installation, users could be offered the option to install as a server on the "main PC," then install as clients on any other machines they plan to use to access the database.
- It would be nice and clean on the clients if the main left browser only displayed the tracks, artists, playlists, etc. from the main database, so the Devices & Services list only shows up on the server itself.
- If there is a way to cache the library data on a client machine so it doesn't have to read 10,000 files every time the tracklist is opened, that would be good.
Upon install on the MMS web interface, there is a message under Menu/Playlists that says "Not implemented - Playlists browsing isn't implemented yet. But it will be!
" That gives me hope that this will happen soon, but since the latest update 3.2 was released in January, I'm not so sure.
I was excited when I read about MMS today (yes, I am behind), because it seemed like the reason it was created was to allow access to a shared library from "client" devices. That's a great idea! It would be like at work, where there is a server running the database, and all the workstations access and manipulate the database, and changes made from any workstation are almost immediately updated to all other workstations.
- Ideally the workstations or clients, whatever you call them, could be other Windows or mobile devices.
- If ultimately MMS becomes part of the MM installation, users could be offered the option to install as a server on the "main PC," then install as clients on any other machines they plan to use to access the database.
- It would be nice and clean on the clients if the main left browser only displayed the tracks, artists, playlists, etc. from the main database, so the Devices & Services list only shows up on the server itself.
- If there is a way to cache the library data on a client machine so it doesn't have to read 10,000 files every time the tracklist is opened, that would be good.
Upon install on the MMS web interface, there is a message under Menu/Playlists that says "Not implemented - Playlists browsing isn't implemented yet. But it will be! ;-)" That gives me hope that this will happen soon, but since the latest update 3.2 was released in January, I'm not so sure.