Comments on: Concurrency Management in Tine 2.0

By: Spirulina

Spirulina — Tue, 19 Aug 2008 21:21:04 +0000

Fajna stronka, bede tu wpadal czesciej, pozdro

By: Cornelius Weiss

Cornelius Weiss — Sun, 06 Jan 2008 22:56:15 +0000

Yes, thats the idea in a second step for the frontend. The screencast only shows the current backend state.

When the backend tells the frontend/client that there is a concurrency problem, the frontend could decide how to handle this conflict. So a merging-helper would be part of the client.

Record locking might be possible if only human clients are involved, but also in this case it could be a problem: What happens if a user don’t close the dialog, or if the client dies?

But the real problem why locking is not an option, are the sync users, e.g. mobile devices. For this kind of clients we need a smart concurrency management anyway.

By: Lutz Falkenburg

Lutz Falkenburg — Sun, 06 Jan 2008 20:19:19 +0000

Wouldn’t it be nice to show the user the differences between his changes and the changes made by another user? Let se user deceide if he would like to merge his changes, forget the other changes made before or cancel his changes…. What about record locking?

Happy New Year!