How to manage long running tasks
How to manage long running tasks
- Subject: How to manage long running tasks
- From: Stefan Pantke <email@hidden>
- Date: Mon, 5 Dec 2005 01:29:00 +0100
I managed to produce printer ready PDF output using
iText. Although iText can't do anything, it is rich enough
for my app.
Now I need to start testing using real-world big image media files.
Don't know exactly right now, but I suppose that these calls may
take some to finish. Probably too much time for my WO default
environment. I'd like to prepare a solution, which works independently
of the current WOA timeout settings.
To prepare a general solution, I'd like to spawn a worker thread,
which takes a job description, computes the result and finally
puts the results aside.
Does WO have a special technique to de-couple lengthy compute jobs? Or
should I just spawn a Java-Thread and attach this to my current
session?
Furthermore, I'd like to prepare some EO objects, which model
running compute jobs and results.
Currently, keeping these objects in a DB store seems to be reasonable.
In general, I'd like to know, if I may create in-memory EO objects,
which
don't get saved to the DB store. Well, this should be possible.
Any ideas how to start reading about this?
_______________________________________________
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