Check out wonder source and run the BackgroundTasks example and look a the 
examples themselves. Also watch the video for that from this year's WOWODC. 
Pascal sent it out to attendees recently.

On Jul 29, 2011, at 4:53 PM, Andrew Kinnie wrote:

> OK, I have done a little searching and poking around in source, and am not 
> finding how one should do the multiple OSCs solution.
> 
> I see there is a property to set to determine the size of the pool, and I see 
> how to get an OSC from a pool, but I don't see anything else about what I 
> need to do to take objects from one stack and put them into a new OSC and how 
> to handle the ec, etc.  Presumably I just need other search terms, but if 
> anyone has an example I can look at that does this sort of thing, I would 
> appreciate it.  I want the task to run in it's own OSC it gets from the pool 
> so that it does not slow down the other concurrent connections (concurrency 
> is now on.  Though I assumed it always was, frankly.)
> 
> Andrew
> 
> On Jul 29, 2011, at 2:56 PM, Kieran Kelleher wrote:
> 
>> 2) For your 1 minute task do it in a background thread and use a different 
>> OSC. Remember EOF is a single-threaded, single-db-connection stack. If you 
>> want high concurrency performance, you cannot just use the default OSC. Use 
>> a ERXTaskObjectStoreCoordinatorPool just for tasks, even if it is just a 
>> pool of one.
> 
> _______________________________________________
> 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/kelleherk%40gmail.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]

Reply via email to