Benoit Maisonny wrote: >> We have implemented something minimal which is inexpensive to implement >> and inexpensive to run. >> >> We think that document authoring is very different from programming. In >> our opinion, locking documents when they potentially can be modified by >> different authors is acceptable. >> > > Please be informed that, in our use cases, there are times when this is not > acceptable.
I understand. > >> That's why we do not plan to go further in terms of concurrent change >> detection. >> > > Our software manages concurrency, change detection and conflict resolution: I guessed that you are using CVS, Subversion, Git, or another version control system. And yes, I know how such systems can detect concurrent changes, for example when you update your working copy. > we don't need you to take care of that. We only need an editor software that > warns the user in due time. I'm sorry if I wasn't clear. I call, "detecting as soon as possible the case where two XXE users modify the same file at the same time", "concurrent change detection" (at the XML editor level, of course).
