> If you need updated information in the rest of the app, do a >refreshing refetch. Isn't this something that would need to be done by the main RR thread(s) on their own contexts?. If so then how will the main threads know when a refretch needs to be done? I don't want them doing refetches for the whole 8 hours just in case there is new data. Or is this a way for the background thread to cause fetches to occur within the main OSC stack?
Also, I really don't want to cause everything to have to refetch when each little bit of new data becomes available, I want each bit to be available as its posted by the background task, and is kind of why I was thinking I'd need to use the same OSC and have the background thread carefully lock and unlock it as needed. Or am I thinking about something wrong here? On Wednesday, July 30, 2008, at 12:53AM, "Guido Neitzer" <[EMAIL PROTECTED]> wrote: >On 29.07.2008, at 22:23, Jeff Schmitz wrote: > >> My first question is, now that I'm using EOs throughout my app >> (including the background process) is there any reason to use the >> WOLongResponsePage if I still don't care about the status page? > >No. > >> I'll save my context locking and memory flushing questions until >> after I've researched the subject a little more. From what I can >> tell though, I'll want to create a new editing context for the >> background thread (not sure about needing an independent Object >> store coordinator for the background process, but I don't think so), >> so that's a start. > >Create a new OSC too, it's safer. > >> Finally, anything in project Wonder that can help me? I did run >> across this: >> >> http://webobjects.mdimension.com/wonder/api/er/extensions/concurrency/class-use/ERXLongResponseTask.html#er.extensions.concurrency >> >> but again, very terse docs. > >It's more a replacement for WOLongResponsePage. Fork a thread and work >there. If you need updated information in the rest of the app, do a >refreshing refetch. > >cug > >-- >http://www.event-s.net > > > _______________________________________________ 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]
