On 27/05/05 16:32 Michael Jouravlev wrote:
* Because you redirect to output action instead of forwarding, it can
be reloaded anytime as many times as needed, either by javascript or
manually by user.
or
http://where.i.was/";>
--
* Call the first action (input)
* Deny service if long process is already running for this client
* Harvest input data and kick off the long process
* Redirect (not forward) to output action, which displays result page
#2 (see below) right away
* Result page #2 must have an auto-refresh javascript
You should make the effort to remove the dependency of the core action
on the request and response objects. Just retrieve the data you need
from the request and response and cache them so that they'll be
available for the duration of your long process. I'm hoping that when
you call it "core actio
Hi all,
we have a struts action which runs in some cases very long (> 1min). In this
case, a firewall between client and server cuts the connection due to
inactivity. To avoid this timeout, we execute the core action in a thread,
while the wrapper action polls the result of the action thread. I
4 matches
Mail list logo
