- July 3, 2011
- 617
- 141
THX for this.
MPSync also hasnt worked for me and always destroyed my DBs.
My setup is the same as yours and also i am coping the DBs from the server to the clients on boot.
Would be really nice if ill could use this and remove trakt.
Will test it and report back.
pOpY[DOUBLEPOST=1422258562][/DOUBLEPOST]Just on question:
Do you "buffer" watched-flags/time changes and sync it again if the server db was locked the first time?
If not this would be nice. Just an idea:
I am thinking on this scenario:

Thanks for bringing this plugin, after the shutdown of follw.it i have waited long for this, because trakt isnt working stable (dont get me wrong,
ltfearme is doing a great job, but the trakt api v2 and servers are unstable).
This is what MP is missing....
thx
pOpY
MPSync also hasnt worked for me and always destroyed my DBs.
My setup is the same as yours and also i am coping the DBs from the server to the clients on boot.
Would be really nice if ill could use this and remove trakt.
Will test it and report back.
pOpY[DOUBLEPOST=1422258562][/DOUBLEPOST]Just on question:
Do you "buffer" watched-flags/time changes and sync it again if the server db was locked the first time?
If not this would be nice. Just an idea:
- 1. Buffer the changes in an concurrent queue (thread safe)
- 2. a worker thread syncs the changes to the master
- 3. if master db is not locked -> lock it -> sync open changes -> release the lock -> remove it from concurrent queue
- or 4. if master db is locked -> wait a few seconds -> try again 3.
I am thinking on this scenario:
- master db is locked -> changes will be sheduled a few seconds back
- User is pressing shutdown -> will changes be lost?
Thanks for bringing this plugin, after the shutdown of follw.it i have waited long for this, because trakt isnt working stable (dont get me wrong,
ltfearme is doing a great job, but the trakt api v2 and servers are unstable).
This is what MP is missing....
thx
pOpY
Last edited: