Home Projects Jobs Clientele Contact


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Database schema

sergey@total-knowledge.com wrote:
>>> 3. Author closes his browser.
>> Cannot handle this.
> I think it's possible. Here is the scenario:
> 1. Set cookie "EditorTimeout" to the user's browser once he starts object
> editing with expiration interval = "the value that UU or admin sets for
> lock timeouts". Use UMO attributes in cookie value.
> 2. Catch "close browser" event using javascript and delete "EditorTimeout"
> cookie from the browser.
> 3. Check if "EditorTimeout" exists for this UMO.
> 4. If not, update the DB for this UMO to make it available(if in DB it's
> still marked as locked).
And how exactly does transition from 3 to 4 happen?
>>> 4. Author clicks on "End Edit Mode" button.
>> What would that do? Cancel changes or what?
> Well, I was thinking that maybe responsible Authors would cancel "lock" by
> themself if, for example, the change that they made to the UMO was very
> quick and there was no need to keep the lock any more. It's in their best
> interest to make their work available, I assume.
Are you saying it's same thing as "Save"?

Ilya A. Volynets-Evenbakh
Total Knowledge. CTO

Authoright © Total Knowledge: 2001-2008