Reply to thread

Message

<blockquote data-quote="lulsam" data-source="post: 745359" data-attributes="member: 28181">Re: Re : Moving Pictures for Servers?In the wiki says: &quot;If you try this, ensure only one client is active at a time.&quot; This seems to me a risky business, isn't it? Also waiting for MePo2 seems a loooooong time as iti is scheduled by the end of 2016 (this is what has been written in the roadmap pages, but maybe it is a developers joke ;-)).I fully agree with most people that believe that some key plugins like Moving Pictures should move to a &quot;client - server&quot; architecture. I don't know how difficult could be to:1.- Re-create the Moving Pictures db3 database schema inside the TVServer database (with its own sepparate schema)2.- Move all the plugin staff from MePo client to the TV Server so it becomes a sever plugin3.- To use Moving pictures on the MePo client there are two options:3.1. being the simple a sync server to client (may an approach like <a href="https://forum.team-mediaportal.com/mediaportal-plugins-47/tool-syncmp-84344/" target="_blank">https://forum.team-mediaportal.com/mediaportal-plugins-47/tool-syncmp-84344/</a> could be enough to start, but a two way sync has teh benefit of being able to dlete or update data from any client). The advantage of this approach is falt tolerance to network issues, the dissadvantage is that requires a sync3.2. Point the clients to use the server db (for me this is the best appoach), and also I believe is the simplest to implement. Pretty similar to the hack described in the wiki, byut with teh advantage of using an advance db on the server side that may prevent client conflicts, for instance, blocking a row when a client is updating it or deleting it based on client idWhat do you think guys? does it make sense?Cheers</blockquote>

[QUOTE="lulsam, post: 745359, member: 28181"] [b]Re: Re : Moving Pictures for Servers?[/b] In the wiki says: "If you try this, ensure only one client is active at a time." This seems to me a risky business, isn't it? Also waiting for MePo2 seems a loooooong time as iti is scheduled by the end of 2016 (this is what has been written in the roadmap pages, but maybe it is a developers joke ;-)). I fully agree with most people that believe that some key plugins like Moving Pictures should move to a "client - server" architecture. I don't know how difficult could be to: 1.- Re-create the Moving Pictures db3 database schema inside the TVServer database (with its own sepparate schema) 2.- Move all the plugin staff from MePo client to the TV Server so it becomes a sever plugin 3.- To use Moving pictures on the MePo client there are two options: 3.1. being the simple a sync server to client (may an approach like [url]https://forum.team-mediaportal.com/mediaportal-plugins-47/tool-syncmp-84344/[/url] could be enough to start, but a two way sync has teh benefit of being able to dlete or update data from any client). The advantage of this approach is falt tolerance to network issues, the dissadvantage is that requires a sync 3.2. Point the clients to use the server db (for me this is the best appoach), and also I believe is the simplest to implement. Pretty similar to the hack described in the wiki, byut with teh advantage of using an advance db on the server side that may prevent client conflicts, for instance, blocking a row when a client is updating it or deleting it based on client id What do you think guys? does it make sense? Cheers [/QUOTE]

Verification