Locking nodes or entities to prevent concurrent editing I have not had a need for this, but another (home built PEAR) CMS I support for a client uses locking to prevent two users from being able to edit a piece of content at the same time. It can be irritating but could prevent loss of work.

I suppose if you have multiple site editors it could be invaluable.

Is it necessary? Is the module content lock a viable option?
I believe this is already implemented to some degree. If two users are editing the same piece of content, and one submits changes, the other user will receive this message when trying to do the same:


  The content on this page has either been modified by another user, or you have already submitted modifications using this form. As a result, your changes cannot be saved.


It happens in the node_validate() function in case you're interested in checking out the code.