Re: WOLongResponsePage and sessions
Re: WOLongResponsePage and sessions
- Subject: Re: WOLongResponsePage and sessions
- From: Guido Neitzer <email@hidden>
- Date: Thu, 7 Aug 2008 11:28:33 -0600
On 07.08.2008, at 11:14, Pascal Robert wrote:
But now I get "broken pipe" errors because IterationStatistiques
take too much time to render. I guess I have to move some processing
from IterationStatistiques to something I can call from
performAction without generating any response until pageForResult is
called :-/
You could generate a page with DirectAction links on it in the
performAction method. That would free you from the context ids on
them. Maybe the generateReponse on that page is doing too much work -
shouldn't that work be done in the performAction and the page should
only "render" the information?
The unlocking is done is the finalize() method.
Just wanted to make sure ... ;-)
cug
--
http://www.event-s.net
_______________________________________________
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