Reply to thread

Message

<blockquote data-quote="m3rcury" data-source="post: 979960" data-attributes="member: 106370">alturismo, et all.&nbsp;Let me explain my setup and how the updates are working.<ul>
<li data-xf-list-type="ul">Master client where I do all the imports. The setup of MPSync on this client is Client -&gt; Server.</li>
<li data-xf-list-type="ul">One other client which is my main viewing client. The setup of MPSync on this client is Server -&gt; Client. This client receives all the changes done on the master client. For convenience, I'll call this client and similarly set up clients as Slave Client.</li>
</ul>The watched/resume updates will follow the path in the opposite direction of the normal updates. i.e. if you are set up as Client -&gt; Server, then the watched/resume path is Server -&gt; Client.&nbsp;To illustrate better, let us take an example setup of 3 clients:<ul>
<li data-xf-list-type="ul">1 Master Client (M)</li>
<li data-xf-list-type="ul">1 Server (S) (a central repository)</li>
<li data-xf-list-type="ul">1 Slave Client (A) on which I was watching a movie/series</li>
<li data-xf-list-type="ul">1 Slave Client (B) on which I want to continue viewing the above movie/series</li>
</ul>The synchronization of imports will follow the below path:&nbsp;(M) -&gt; (S) -&gt; (A)(B)The update of watched/resume status will follow the below path:&nbsp;(A) -&gt; (S) -&gt; (M) -&gt; (S) -&gt; (B)As you can see, the current process requires that the Master Client is available at all times for the synchronization to work. I was thinking of altering this to synchronize the watched/resume status even when Master is off, but it is a bit more complex and requires some more time.&nbsp;Can you check if your setup is in line with the above and advise.</blockquote>

[QUOTE="m3rcury, post: 979960, member: 106370"] alturismo, et all. Let me explain my setup and how the updates are working. [LIST] [*]Master client where I do all the imports. The setup of MPSync on this client is Client -> Server. [*]One other client which is my main viewing client. The setup of MPSync on this client is Server -> Client. This client receives all the changes done on the master client. For convenience, I'll call this client and similarly set up clients as Slave Client. [/LIST] The watched/resume updates will follow the path in the opposite direction of the normal updates. i.e. if you are set up as Client -> Server, then the watched/resume path is Server -> Client. To illustrate better, let us take an example setup of 3 clients: [LIST] [*]1 Master Client [B](M)[/B] [*]1 Server [B](S)[/B] (a central repository) [*]1 Slave Client [B](A)[/B] on which I was watching a movie/series [*]1 Slave Client [B](B)[/B] on which I want to continue viewing the above movie/series [/LIST] The synchronization of imports will follow the below path: [INDENT=1][B](M) -> (S) -> (A)(B)[/B][/INDENT] The update of watched/resume status will follow the below path: [INDENT=1][B](A) -> (S) -> (M) -> (S) -> (B)[/B][/INDENT] As you can see, the current process requires that the Master Client is available at all times for the synchronization to work. I was thinking of altering this to synchronize the watched/resume status even when Master is off, but it is a bit more complex and requires some more time. Can you check if your setup is in line with the above and advise. [/QUOTE]

Verification