Concurrency when Editing

[rickybanister]

In the future we should work out a way to put in some Concurrency.

When the 'edit slot' button is clicked, it should pass something to the filter, then other users see that slot is disabled, or a message appears informing them that so-and-so is editing and to be careful. We can decide later if editing should be locked until the save button is clicked, or if it should just do a better job of informing you that both versions are in the history.

The history is going to need to be a little more robust maybe.

[boutell]

We probably don't have to lock it because we use transactions for new area versions (or anyway we should, I'll check as part of this ticket). Which is good because People Walk Away and there's no good way to be certain that someone is no longer editing.

We could implement an I'm-still-here ajax call for edit views that keeps the concurrency notice up for others as long as it's been received recently, with a corresponding bye-bye-now ajax call if the user saves or cancels.

Such a call would also address the session timeout problem, although we might want to put a timeout back in somehow as this could itself be regarded as a bad thing.

[johnnyoffline]

This would be awesome, like google spreadsheets when you can see someone is editing.

It would make working on the site a lot of fun.

Oh there's Rick on the about page writing about it his pitbull, Lima Bean

[tboutell]

This should not be a 1.5 ticket, it is not on the shortlist already and it's a big deal. We need to finish 1.5