Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of jh@schaubroeck.be designates
 193.75.212.6 as permitted sender)
Message-ID: <43F05FF6.6090509@schaubroeck.be>
Date: Mon, 13 Feb 2006 11:31:18 +0100
From: Jan Hoskens <jh@schaubroeck.be>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: continuations
References: <43F05185.1060609@schaubroeck.be>
    <OF24F8C4FF.679543A0-ONC1257114.0034B889-C1257114.0034FDD1@sofico.be>
 <1553.10.10.31.43.1139825717.squirrel@10.10.31.43>
In-Reply-To: <1553.10.10.31.43.1139825717.squirrel@10.10.31.43>
Content-Type: multipart/alternative;
 boundary="------------050101090909090003080404"

--------------050101090909090003080404
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Fabrizio Sitzia wrote:
> 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...
>   
That's correct, I'll definitely check that session-bound-continuations 
attribute, thanks for the info.
> - 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>
>   
I don't want my sessions/continuations to have long time-out periods for 
security reasons. It's ok to have them log in again if their session is 
timed out after eg a half hour. But then again, when they are editing a 
form, this might take some time, and the responsibility of keeping this 
form window open/uncommitted is completely on their side. So if they are 
off to McDonalds during editing, it's their own decision to leave that 
window open.

Kind Regards,
Jan

>
> Fabrizio
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>   

--------------050101090909090003080404
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Fabrizio Sitzia wrote:
<blockquote cite="mid1553.10.10.31.43.1139825717.squirrel@10.10.31.43"
 type="cite">
  <pre wrap="">Hello,

  </pre>
  <blockquote type="cite">
    <pre wrap="">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...
    </pre>
  </blockquote>
  <pre wrap=""><!---->
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...
  </pre>
</blockquote>
That's correct, I'll definitely check that session-bound-continuations
attribute, thanks for the info.<br>
<blockquote cite="mid1553.10.10.31.43.1139825717.squirrel@10.10.31.43"
 type="cite">
  <pre wrap="">
- I also set the servlet container's (Jetty) session-timeout to 4 hours
  (240 minutes), by adding the following to its "web.xml" file:

    ...
    &lt;session-config&gt;
      &lt;session-timeout&gt;240&lt;/session-timeout&gt;
    &lt;/session-config&gt;
  &lt;/web-app&gt;
  </pre>
</blockquote>
I don't want my sessions/continuations to have long time-out periods
for security reasons. It's ok to have them log in again if their
session is timed out after eg a half hour. But then again, when they
are editing a form, this might take some time, and the responsibility
of keeping this form window open/uncommitted is completely on their
side. So if they are off to McDonalds during editing, it's their own
decision to leave that window open.<br>
<br>
Kind Regards,<br>
Jan<br>
<br>
<blockquote cite="mid1553.10.10.31.43.1139825717.squirrel@10.10.31.43"
 type="cite">
  <pre wrap="">

Fabrizio


---------------------------------------------------------------------
To unsubscribe, e-mail: <a class="moz-txt-link-abbreviated" href="mailto:users-unsubscribe@cocoon.apache.org">users-unsubscribe@cocoon.apache.org</a>
For additional commands, e-mail: <a class="moz-txt-link-abbreviated" href="mailto:users-help@cocoon.apache.org">users-help@cocoon.apache.org</a>

  </pre>
</blockquote>
</body>
</html>

--------------050101090909090003080404--