WOLongResponsePage
WOLongResponsePage
- Subject: WOLongResponsePage
- From: Jeff Schmitz <email@hidden>
- Date: Tue, 29 Jul 2008 23:23:05 -0500
Hello,
I have the need to kick off a VERY long (i.e. possibly up to 8-10
hour) background task that before it's through fetches most of the
contents of the database (via EO's of course) and performs
calculations on the data and saves the calculated values back to the
EOs many times during the process. And oh, I'd like to have the
results available to the rest of my app as they are saved by the
background task.
Currently btw, I do this with a java thread and don't really use EOs,
and I just return a page immediately after the thread is kicked off,
i.e. I don't really care about a status page reloading for 8 hours as
I'm the only user that actually kicks off this process.
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? If
so, there seems to be a dearth of information on exactly how to use
such a component. All I can really find is a very terse API doc, and
a few mentions of its existance on the wiki. Any examples out there
anywhere?
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.
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.
Thanks,
Jeff
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden