Re: How to manage long running tasks
Re: How to manage long running tasks
- Subject: Re: How to manage long running tasks
- From: Stefan Pantke <email@hidden>
- Date: Mon, 5 Dec 2005 17:33:07 +0100
Am 05.12.2005 um 12:25 schrieb Helge Staedtler:
I think I have put together what you might need a time ago. have a
look at
www.wocode.com there you will find code and tutorial explaining
LongResponses by example.
http://wocode.com/cgi-bin/WebObjects/WOCode.woa/wa/ShareCodeItem?
itemId=291
This way your Session-timeout does not matter, because the page gets
refreshed all the time as long as the response generates results.
Thx, Helge, really nice hint. Just learning, where to find the
important things in WOrld ;-)
Currently, I'd like to spawn somehow a long running requests and keep
the spawned thread keep running, as long as there is something to do -
even if the user logs off. I suppose the refresh-technique is a special
case here. Thus the user thread might probably not be the best idea.
Let's see.
it off in an extra-Thread seems reasonable, but what do you mean
with "Currently, keeping these objects in a DB store seems to be
reasonable."? Images or as you said "real-world big image media
files" in
the DB? Sounds like a really bad idea to me.
Yes, you are right, I'd like to put the resulting image somewhere
on disk and keep its full path in the DB while switching the job's
state from kRunning to kReady - or something like that.
By object, I meant the job description object.
Cheers,
Stefan
_______________________________________________
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