4,216
edits
Changes
→Concurrent access problems
Furthermore, the following must be taken into account:
*For safety, opposed to what GRAMPS does, only changesets are done, not write of the entire object. So one does not save a person, one saves a changed name of a person. The way GRAMPS changes everything everytime one clicks on safe was not a good decision way back, but understandable in a single user environment
*The client must be able to work sensible with a fail on save. In essence, in GRAMPS speak, this means a person-update, family-update, .... signal has happened since the view was constructed, and the view must update itself like the GRAMPS views/editors do on recieve receive of such a signal. Javascript magic can do this easily ??
There seem to be two modes for concurrent edits on the web: something like what this wiki uses, and something more complicated using AJAX. I think we should make this as simple as possible for the following reasons: