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
Development
General Development (no feature request here!)
Database: Refactor MP1 database for multi seat usage
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: 1288568" data-attributes="member: 153283"><p>Just on another point. The refactored version was developed to enable multi-user client databases to be viable. One failing in the current refactored release is that the system doesn't know which client machine initiated a database update. To fix this, I propose to add an extra parameter in the config file called "client" where the client name can be specified (alongside "version"). I think this would be a simpler way to handle this issue than to have user logons (as MP2 allows).</p><p></p><p>I want the code to be able to feed back to each other client when data has been changed by another client. Obviously, this would require validation to be performed when MP opens to ensure that the client name is unique for the system.</p><p></p><p>If anyone has a better way of achieving this, please let me know.</p><p></p><p>I could create a separate database that stores client information. I think this approach would be more reliable than using the config files but would be slightly more work. I've used this approach for another system so could borrow that code to use here.</p><p></p><p>Any ideas welcome.</p></blockquote><p></p>
[QUOTE="Anthony Vaughan, post: 1288568, member: 153283"] Just on another point. The refactored version was developed to enable multi-user client databases to be viable. One failing in the current refactored release is that the system doesn't know which client machine initiated a database update. To fix this, I propose to add an extra parameter in the config file called "client" where the client name can be specified (alongside "version"). I think this would be a simpler way to handle this issue than to have user logons (as MP2 allows). I want the code to be able to feed back to each other client when data has been changed by another client. Obviously, this would require validation to be performed when MP opens to ensure that the client name is unique for the system. If anyone has a better way of achieving this, please let me know. I could create a separate database that stores client information. I think this approach would be more reliable than using the config files but would be slightly more work. I've used this approach for another system so could borrow that code to use here. Any ideas welcome. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Database: Refactor MP1 database for multi seat usage
Contact us
RSS
Top
Bottom