Hi James,
Another thread may help, but for long EOF intensive tasks, a new
ObjectStoreCoordinator (new db connection) can be better. I have some
long processes that hammer the db generating report data for 10 to 15
seconds and I find this approach works well to not block all users of
the app. It also is much faster.
// Create a new EOF stack (includes new connection to the db)
EOObjectStoreCoordinator longTaskCoordinator = new
EOObjectStoreCoordinator();
// Use the separate EOF stack
EOEditingContext ec = new EOEditingContext( longTaskCoordinator );
NSArray objects = ec.objectsWithFetchSpec ..... etc.
Cheers, Kieran
On Dec 4, 2006, at 9:53 PM, James Cicenia wrote:
Hello -
I have created a nice custom report generator based upon D2W and it
works
like a charm except for the occasional bad problem.
If a person doesn't filter the selection and pulls all the data
with all the attributes
it can cause my server to basically deny others.
Do I have to put this process in a different thread? Do I have to
use a long response
page?
Thanks
James Cicenia
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/kieran_lists%
40mac.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
