-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 s
ty with me. 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 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
ow)"... 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
w
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
> 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 o
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 H
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 session timeout value. I also do
not want to pu
On 4/28/07, lightbulb432 <[EMAIL PROTECTED]> wrote:
What would the cookie store?
A Cookie stores name, value pairs just like the Session. So you can
store anything in a Cookie.
But I think it may be a security concern to store the password in a Cookie.
Username and password, just username,
start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Keep-session-alive-tf3662662.html#a10234725
Sent from the Tomcat - User ma
On 4/28/07, lightbulb432 <[EMAIL PROTECTED]> wrote:
Is it possible for a Tomcat session keep the session alive for a certain
period of time (say, 2 hours),
The session timeout interval is adjustable, see under
conf/web.xml
Max inactive interval can also be specified in HttpSession object,
wi
esn't eat up Tomcat memory.
--
View this message in context:
http://www.nabble.com/Keep-session-alive-tf3662662.html#a10234242
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-m
12 matches
Mail list logo