If you want to do it like that, I'd suggest a new Result... Like the chaining result, but asynchronous instead... Then you can start by chaining now, and move to the async chain later...
> -----Original Message----- > From: Aaron Held [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 03, 2004 2:49 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Long running tasks > > > Jason Carreira wrote: > > >You could create a new Dispatcher that takes a namespace and Action > >name and will kick off a separate thread to execute them... > You could > >use the Session to save status information for asynch Action > execution. > > > > > > > This sounds like the answer I was looking for. > So I can build the Action now without worrying threads and when the > delay becomes too long convert it to an seperate thread. > > Thanks, > -Aaron > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President > and CEO of GenToo technologies. Learn everything from > fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
