Hi Chuck

I'm moving this over to the wonder list:

Yes. EOF is single threaded at the point of fetching and saving. Your best option is probably to create a separate EOF stack for these long running process. Beware of using default....() methods with this stack.

ok, bummer.


See
- MultiOSCFactory in Wonder, - bottom of http://www.wirehose.com/ developer/DeveloperGuide/MacOSX/Contents/ Importing_in_a_separate_thread.htm

oh, good, that was the part i was missing.
So, I'd like to start using ERXObjectStoreCoordinatorPool. And I have some questions:

1. I used ParticipatingEC to extend ERXEC. It would be pretty easy to convert to using pure ERXEC, but sometimes I need to turn off the will/did methods called by ERXGenericRecord, per editing context created.
        I don't see an obvious way to do this? Is it possible?

2. If I understand correctly when I up the value of maxCoordinators each session will get it's own stack. That's fine I guess, though I'd prefer if i could either manually tell an editing context to use it's own stack or not. I'm quite happy with sessions sharing a stack, but sometimes I kick off a long fetch (using a long response) and I'd like to use a separate stack only for that thread. there are several reasons (this is the first time i venture to this depth so forgive if anything here is naive). One reason is that I don't actually deal with objects that affect the session stack, the other is that when that request has run i can garbage collect those objects and get rid of the editing context, and hopefully freeing up that memory again.

3. How do I use the ERXObjectStoreCoordinatorPool with plain jdbc (i use jdbc to stream assets to the db)?

Thx for any answers and pointers

regards

Cornelius
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to