Best Practice EC Locking for Direct Actions/Concurrent Requests
Best Practice EC Locking for Direct Actions/Concurrent Requests
- Subject: Best Practice EC Locking for Direct Actions/Concurrent Requests
- From: Hunter Hillegas <email@hidden>
- Date: Tue, 4 May 2004 15:41:10 -0700
I have been following the locking discussion and it has been very
helpful, thanks.
We have an application that uses a lot of DirectActions to display data
to the user. They often contain ECs that are used to fetch data from
the DB for display. With the locking logging turned up, they generate a
lot of complaints from EOF for locking violations...
This application has concurrent requests turned ON.
What is the best practice for locking/unlocking ECs used in this way?
Will locking the EC used to fetch data in a DirectAction block other
users that are using the application concurrently (via concurrent
request handling)?
When fetching data for a page accessed via a DirectAction, is it
considered better to do the fetch in the component constructor or the
calling DirectAction?
Thanks,
Hunter
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.