You can have multiple EOF stacks by creating new
EOObjectStoreCoordinators. Wonder has features that easily enables
multiple EOF stacks and also for synchronizing changes between them in
the same instance and across many instances.
I use java.util.concurrent stuff all the time for background
operations using thread pool. Just don't pass EO's and ec's between
threads .... pass EOGlobalIDs between threads and create, lock and
unlock editing contexts in your background threads.
On Feb 5, 2009, at 10:09 PM, Karthik N wrote:
Hi,
I'm a WO 5.4 newbie. We have a WO app that uses EOF for db access.
I believe this makes the WO inherently single-threaded.
We have this new requirement wherein, we want to have a thread-pool
via java Executor within this WO app for non-EOF purposes to perform
some asynchronous background tasks.
Is it safe to have such a thread pool without jeopardizing the WO
app in any way?
Thanks, Karthik
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/kieran_lists%40mac.com
This email sent to kieran_li...@mac.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
