More > JRiver Media Center 32 for Windows

Design: Download Library from Server

(1/6) > >>

JimH:
I'd like your help in thinking through how we build a new capability, one that can move a library to a new machine, including files, database and settings.

In the Tools Menu, when you connect to a remote Library Server, there is a "Download from Server" feature.  We may just need to add a "Download Library from Server".

It would move all selected files (or all files) to the connected client.  It would ask whether to include playlists, settings, etc.  These could probably be moved as a backup file.

MC would make an assumption about the default locations, but allow you to change them.

JimH:
On the client side, MC would need to unpack the backup file from the server, then compare the backup's locations to the desired locations.  It might be enough to just move the root locations and leave the rest as is.

It needs to check for available disk space and report that to the user.

JimH:
If we do this well, it may also serve as a backup mechanism.

This2ShallPass:
I can see that this would be incredibly powerful. I also think that consideration should be made to include ways to migrate whole libraries to/from JRiver Id devices.

zybex:
This requires consideration and conversion of fwd/back slashes between different OS, and also perhaps composed/decomposed UTF character encodings when copying to/from MacOS.

One useful derived feature is a simple "offline DB" checkbox, where the local cached DB can work independently from the server for a while (with a big red label saying "OFFLINE MODE" somewhere). The issue here is how to synchronize DB changes when the client comes back online and reconnects to the server - one way is to just make it read-only and drop any changes that were made on the client, perhaps with a warning. Or, attempt to sync and detect conflicts.

Navigation

[0] Message Index

[#] Next page