On 23/11/2010 17:58, Aggarwal, Ajay wrote:
I have a situation where client enters a long duration request and I
need to keep the session alive for the client while this long duration
request is going on. Since this long duration request could be hours, I
do not want to change the default HTTP
From: Aggarwal, Ajay [mailto:ajay.aggar...@stratus.com]
Subject: how to keep session alive on the server side
I have a situation where client enters a long duration
request and I need to keep the session alive for the
client while this long duration request is going on.
Since this long
Aggarwal, Ajay wrote:
I have a situation where client
what kind of client ?
enters a long duration request
do you mean that the request takes a long time to send to the server, or that the server
will take a long time to respond ?
and I
need to keep the session alive for the client
?
)... or
some other trick.
-Original Message-
From: André Warnier [mailto:a...@ice-sa.com]
Sent: Tuesday, November 23, 2010 2:47 PM
To: Tomcat Users List
Subject: Re: how to keep session alive on the server side
Aggarwal, Ajay wrote:
I have a situation where client
what kind of client ?
enters
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
On 11/23/2010 1:46 PM, Caldarale, Charles R wrote:
From: Aggarwal, Ajay [mailto:ajay.aggar...@stratus.com]
Subject: how to keep session alive on the server side
I have a situation where client enters a long duration
request and I need
. So
I can't use a negative value either (i.e. never expires).
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Tuesday, November 23, 2010 4:08 PM
To: Tomcat Users List
Subject: Re: how to keep session alive on the server side
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ajay,
On 11/23/2010 4:15 PM, Aggarwal, Ajay wrote:
I am little reluctant to use HttpSession.setMaxInactiveInterval() for
couple of reasons:
1) I don't know ahead of time how long these operations will take. So
I don't have a good value to set
