That doesn't sound like it should be the responsibility of the transfer object. If only one person can edit at a time, your application should enforce those rules.
- Gabriel On Fri, Oct 2, 2009 at 6:51 PM, John Watson <[email protected]> wrote: > Sorry, I probably should have given an example when i first posted the > question. > Say there is a page to view/edit contact information of a person. User1 > opens John Doe to view/edit (also placing a lock on the object). User2 comes > along and also opens John Doe, the user would be able to view contact > information but not make any edits until User1 navigates away from the page > or until the lock times out. > I've made a simple implementation using a decorator (though object.clone() > breaks the functionality because my lock isn't in the transfer object). I > was more wondering if something already existed to do this or if there were > any plans for it? > Thank you, > John > On Fri, Oct 2, 2009 at 14:53, Mark Mandel <[email protected]> wrote: >> >> Sorry... I'm not sure what you are asking. >> >> Can you explain a bit more? >> >> Mark >> >> On Thu, Oct 1, 2009 at 6:34 PM, John Watson <[email protected]> wrote: >>> >>> Is there a way to currently to lock objects (grant exclusive write >>> access to a session)? >>> >> >> >> >> -- >> E: [email protected] >> T: http://www.twitter.com/neurotic >> W: www.compoundtheory.com >> >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
