home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Plugins
[Plugin] MPSync - MediaPortal multi-seat Synchronization
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Anthony Vaughan" data-source="post: 1269641" data-attributes="member: 153283"><p>Hi nyt</p><p></p><p>I have had a look at Moving Pictures and MP_TVSeries and I think I have a solution. I had developed a Sync app that only processed the Video database. I have now re-developed the app from the ground up to develop any database, but with one caveat - the databases are divided into two categories; primary or non-primary.</p><p></p><p>Primary databases are:</p><p></p><p>Fanart;</p><p>Folder;</p><p>Music;</p><p>Picture;</p><p>Video.</p><p></p><p>Non-primary will be any other database.</p><p></p><p>Primary databases require considerable development to synchronize, whereas non-primary databases are simply captured by a file watcher and copied to all other clients or to a queue when files are locked. This adjustment to my strategy at least allowed me to offer a versatile solution with a reasonable development time. BTW, you don't HAVE TO declare primary databases as primary in my app. For example, if you know that your system will only process the picture database from one client at a time, then you can safely declare the picture database as a non-primary database. It will then be copied to all clients without detailed processing - far faster than the alternative.</p><p></p><p>The primary databases will be processed record by record to apply any changes and copied to all clients. Non-primary databases will only be copied to clients.</p><p></p><p>For this to work, users will need to take care to avoid running non-primary databases using processes that update the database from more than one client at a time.</p><p></p><p>The app is a real-time, peer to peer, sync application, using a separate database to store client databases changes for primary databases and applying the changes to all clients. The app must be installed on a machine running 24/7; preferably not the MP server machine, otherwise client changes may be lost.</p><p></p><p>Let me know if you are interested in trying it out. I have been using it for over a year in its earlier version without issues, but have only just finished testing the latest version - with primary and non-primary databases.</p><p></p><p>Tony</p></blockquote><p></p>
[QUOTE="Anthony Vaughan, post: 1269641, member: 153283"] Hi nyt I have had a look at Moving Pictures and MP_TVSeries and I think I have a solution. I had developed a Sync app that only processed the Video database. I have now re-developed the app from the ground up to develop any database, but with one caveat - the databases are divided into two categories; primary or non-primary. Primary databases are: Fanart; Folder; Music; Picture; Video. Non-primary will be any other database. Primary databases require considerable development to synchronize, whereas non-primary databases are simply captured by a file watcher and copied to all other clients or to a queue when files are locked. This adjustment to my strategy at least allowed me to offer a versatile solution with a reasonable development time. BTW, you don't HAVE TO declare primary databases as primary in my app. For example, if you know that your system will only process the picture database from one client at a time, then you can safely declare the picture database as a non-primary database. It will then be copied to all clients without detailed processing - far faster than the alternative. The primary databases will be processed record by record to apply any changes and copied to all clients. Non-primary databases will only be copied to clients. For this to work, users will need to take care to avoid running non-primary databases using processes that update the database from more than one client at a time. The app is a real-time, peer to peer, sync application, using a separate database to store client databases changes for primary databases and applying the changes to all clients. The app must be installed on a machine running 24/7; preferably not the MP server machine, otherwise client changes may be lost. Let me know if you are interested in trying it out. I have been using it for over a year in its earlier version without issues, but have only just finished testing the latest version - with primary and non-primary databases. Tony [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
[Plugin] MPSync - MediaPortal multi-seat Synchronization
Contact us
RSS
Top
Bottom
