Hi Piotr, On Nov 16, 2010, at 4:19 PM, Piotr Dziubecki wrote:
Dear all,
I've started similar topic on xwiki-users list, but it got to the stage I would like to continue with you and your opinions.
What I'd like to achieve are section locks. Just a brief context:
Currently users can do concurrent editing but it's somewhat simplified and could lead to data loss. The lacking part of that process is well described in this old jira issue pointed out by Sergiu:
http://jira.xwiki.org/jira/browse/XWIKI-175
That would need to create procedure checking whether something has changed since user opened a document to edit and if so get him to merge screen. Now it's just saving latest data over the previous changes.
That should be done, but what would help right away to limit such errors is to add more granularity to the document locks. Now when user edits a section within a page other users see the message
"This object is currently locked by.."
which is confusing for them because they might want to edit different section simultaneously and then there is no conflict at all.
I would like to get your advices how that could be achieved, Sergiu answered to my question in the following way:
Could you tell whether the sections are introduced only for the presentation layer, to facilitate editing or they are also mapped to the application's model ?
Somewhere in between. The whole content is stored in one piece, but there are some APIs to access sections.
Here you have the original thread: http://lists.xwiki.org/pipermail/users/2010-November/022404.html
Could someone elaborate a little bit more on this topic ?
Not sure what you're looking for exactly. Let me summarize what I think the status is on this: - everyone here is ok that have section level locks - in the farther future we'd like better locking solution like no conflict (which was researched in Concerto and continues now in Wiki 3.0's research project) - if you provide a patch it can be committed, provided it includes automated tests and follows xwiki's project coding conventions (if it doesn't it can still be considered for inclusion but it may take longer since a committer would need to adapt the patch first before committing it). See also http://dev.xwiki.org/xwiki/bin/view/Community/Contributing Let us know if you need more details. Thanks -Vincent