Reply to thread

Message: <blockquote data-quote="JonJon" data-source="post: 550516" data-attributes="member: 50110">Thank you both for responding, I've got some follow-up questions for you!1. How would you define a client? A machine or a user. The reason I ask is that if I was to make the toggle status per client the definition would determine if I use a local database for storage or not. If its by user then it would require the user to login (just a pincode?) but they would be able to use their configuration and setting on any machine.2. Is a restricted/locked mode and unrestricted mode preferred to the above? i.e. all clients will run in a restricted view mode (filter out content by classification?) until the pincode is entered and then everything is available.3. If we are going to have watch status per client then what else should be? Views?4. Would you prefer to have the plugin watching shared folders and import to a central location(repository) or as it currently is. This is mostly for ppl that download/rip episodes on a different computer and would allow some nice file name formatting when importing.I'll give you a brief outline of how I see this working, let me know if you see any faults or enhancements.A windows service will run on your server, this will handle all the back-end processing of the current plugin, that is watching for new files to import, downloading tv series info and images from thetvdb.com. It will have either an SqLite, MS SQL or MySQL database that stores the global configurations. Clients will query the service using network protocols and access episodes via UNC paths (Shared Folder/s). Images will be cached locally, although I am tossing up if this should be configurable but not sure what the impact of responsiveness will be like if clients access images directly. They may also have a SqLite database for local configuration and status should we go the route of per client settings.</blockquote>

Verification