Re: Database schema

[sergey@total-knowledge.com]

Events that cause a timeout to end and make the UMO available for others:
1. Timeout is expired.
2. Author publishes the UMO.
3. Author closes his browser.
4. Author clicks on "End Edit Mode" button.
5. Author selects "Versioned" radio button and clicks "Save" button.
6. Author tries to link this UMO to others or link any other UMO to this UMO.

Events that do not cause timeout to end:
1. Author hits "back" button in his browser.
2. Author clicks on any link other than "Publish", "End Edit Mode".

I'm not sure about scenario 3. Please give me your feedback, add other
scenarios. It will help me to figure out which functionality will be
available for users in "edit mode" and which parts will be hidden from
editors(if any).


> There was a bit of confusion as to what this lock is going to affect,
> and what its purpose, which we resolved with Alexey on IRC.
>
> To repeat that for benefit of all others:
>
> 1. Purpose of this lock is to avoid two authors modifying same
> object at the same time, thus introducing conflicting changes.
>
> 2. Effect of locking UMO is to prevent any other author from
> opening said UMO for editing.
>
> 3. Purpose of timeout on the lock is to ensure that object does
> not get accidentally locked forever.
>
>
> --
> Ilya A. Volynets-Evenbakh
> Total Knowledge. CTO
> http://www.total-knowledge.com
>
>