Hello,
> I have a flow in which I create a form. When this form is displayed, I
> like to keep the continuation to stay alive for as long as the user is
> filling in that form (which can take more than one hour, depends on how
> many times the user is refilling his cup of tea or coffee, and how many
> colleagues are passing by to have a nice chat with...
Yep, and people tend to get very upset if they spent 5 minutes beginning
to fill out a form just before they left for a 2 hour lunch, and find
their session has expired when they come back!
For a less security-critical intranet app, I therefore defined a timeout
of 4 hours, as follows:
- In "cocoon.xconf", I set the continuations-manager's time-to-live"
attribute to 14400000 (4 hours * 3600 seconds * 1000 milliseconds :-)
I also set the "session-bound-continuations" attribute to "true", as
there is no point leaving continuations around when the servlet
container's session has expired...
- I also set the servlet container's (Jetty) session-timeout to 4 hours
(240 minutes), by adding the following to its "web.xml" file:
...
<session-config>
<session-timeout>240</session-timeout>
</session-config>
</web-app>
Fabrizio
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
