> >> All this assumes that we aren't going down the road of: User > >> can't even open the page because user B has that page locked > >> (opened). > > > > That's really not possible over http (well, possible, but not > > reliably so). > > Well, it is possible using pessimistic locking (HTTP's not involved) > - but I think for a CMS, optimistic would be the way to go.
But pessimistic locking requires that the object be manually locked and then unlocked - It requires statefulness. If a user goes to edit a page, the app locks the page and the user closes their browser, when does the object get unlocked? You could do it in a roundabout way be making the edit page constantly set a 'I'm on ur page editing ur data' request using ajax that updates a 'last locked' field in the db, but it's messy messy messy. Dan. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
