More > Media Center 17

Further Client/Server development?

<< < (2/7) > >>

Mars:
Thanks for your advice, Glynor  ;)

My comments were initially in the "Where We're Going Next" thread ( http://yabb.jriver.com/interact/index.php?topic=66587.msg450456#msg450456 ) which was a more generalist one, not so specific, but when a bit of discussion started I was requested to move to a new thread. So I was just trying to open a discussion on how did people manage their data and put the example of what many of us have at work with ERP systems based on client/server schemes, in which full control is granted from any workstation, depending on the user credentials.

My main aim is not having to do any library managing physically at the server.

As you said, there have been many improvements, but I still have to be quite stealthy with the sync mechanism since there are things that apparently can be modified from the client but then changes are not reflected on the server.

As requested and to be more specific, these are some of the things I missed whenever I tried to manage the library from the client side that still can't be done, as far as I'm concerned:


* Configuring Theater View (So I wouldn't have to interrupt the playback and "steal" the display of the HTPC)
* Configuring View Schemes
* Renaming Files (under library tools) after a tagging work is made
* Assigning Cover Art and saving to the file folder
* Deleting Playlists
* Using more than one hosted library
* User Accounts System with permission for viewing and/or editing data, modifying configurations and settings,...

MrHaugen:
You're touching some important things. Especially this with view management and a User Account System or Access Control Lists system to prevent access for certain users, or prevent alteration of data like Number Plays etc, or other tag manipulations. It's not before this is implemented that we will see the true potential of a server/client relationship. It could be used in a lot of cases like homes, to separate libraries for different family members, to prevent modify rights to customers in your store, share the library with friends, limiting access on devices that have specific purposes etc etc.

The thing with views is that the views should also be individual. Now, you get the views that is configured on the server. This is not great in case you want several clients with different purposes. The attached illustration that was created some weeks ago when we touched the subject of View management. It's a possible solution at least. The illustration consists of two selectable views, where you can drag and drop items, copy, move etc. Thing's can be stored for user created groups, and synced to given clients.

Mars:
Thanks for your reply, MrHaugen  :)


--- Quote from: MrHaugen on October 25, 2011, 04:31:10 am ---The thing with views is that the views should also be individual
--- End quote ---

Yes, I would definitely add this to the list. I like the profiles system suggested, in which one could sit in front of any PC at home, log in MC with its credentials and have its own profile with its preferred view schemes and permissions. It could also be used to assign dedicated functions to different computers at home.

MrHaugen:
Remember that this suggestion/illustration does not take into account access to Media on the server. Another management interface would be needed for that. But the groups in this example could very well be tied to a access control system. One example would be lockdown of theater view, a user/group selection via the primary roller in the main menu and a touch screen interface for a short code for each user or group. Or a credential popup when connecting to a new library server. Which could also be saved on the client. I could finally start to add music only client on my bathroom, video and music only client on my kitchen, as well as sharing my library with friends and family without the risk of them messing up the tags. It would be a server/client nirvana imo.

Mars:

--- Quote from: MrHaugen on October 25, 2011, 05:46:52 am ---Remember that this suggestion/illustration does not take into account access to Media on the server
--- End quote ---

However, view limitation would also somehow prevent access, so it would work in that way, wouldn't it?


--- Quote from: MrHaugen on October 25, 2011, 05:46:52 am ---I could finally start to add music only client on my bathroom, video and music only client on my kitchen, as well as sharing my library with friends and family without the risk of them messing up the tags. It would be a server/client nirvana imo.
--- End quote ---

This is nice for the user "consumer", but I'm also really interested in the "editor", that is, the user who modifies the library. As I said, I'm trying to avoid any data edition or configuration phisically on the server.

Navigation

[0] Message Index

[#] Next page

[*] Previous page