Direct Action App Editing Context management?
Direct Action App Editing Context management?
- Subject: Direct Action App Editing Context management?
- From: Kieran Kelleher <email@hidden>
- Date: Wed, 9 Feb 2005 10:58:03 -0500
How do you handle managing (lock/unlock) timing of editing contexts in a direct action app that does not have a session?
Normally I use session awake and sleep to lock/unlock peer editing contexts. At the page component level, could an EC that is passed from page to page be locked at the beginning of takeValuesFromRequest and unlocked at the end of appendToResponse, albeit that appendToResponse might be a different page and assuming that a reference to the EC was passed to that next page. Sort of like having a MultiECLock Manager built into a Page WOComponent subclass that every page in the app subclasses?
Is it feasible at all, or do you just always switch into session mode when you start working with data editing and stick with direct actions for read only segments of apps using the shared editing context to fetch data for display?
-Kieran
________________________________________________________________
Blog: http://webobjects.webhop.org/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden