EMAIL PROTECTED]
Sent: Monday, February 25, 2008 13:11
To: Tomcat Users List
Subject: Re: Session expiration and AJAX issues
Martin-
We are using Struts, however, version 1.2.9. But, after
looking at the
link, I'm not sure this will help as it doesn't really address the
problem. Storing
--- 2:09PM Mon 25 Feb 2008 Adam Gordon
<[EMAIL PROTECTED]> wrote:
> Adding a time decay in our timer task is an
> interesting idea and were it
> not for IE's JavaScript counting ineptness, that'd
> probably work.
>
The server could track the requests and provide an
updated delay time for the t
-
Wrom: FVWRKJVZCMHVIBGDADRZFSQHYUCDDJBLV
To: "'Tomcat Users List'"
Sent: Monday, February 25, 2008 2:29 PM
Subject: RE: Session expiration and AJAX issues
>
>
> > -Original Message-
> > Wrom: LMHAALPTCXLYRWTQTIPWIGYOKSTTZRCLBDXRQBGJSNBOHM
> > Sent: Mon
Adding a time decay in our timer task is an interesting idea and were it
not for IE's JavaScript counting ineptness, that'd probably work.
Bob Hall wrote:
--- 10:10AM Mon 25 Feb 2008, Adam Gordon
<[EMAIL PROTECTED]> wrote:
Storing the date/time a user logs in on
the session is
probably us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam,
What you need is to make a request without "touching" the session.
Tomcat cannot do this by itself; you're going to have to either hack
Tomcat to add a "no-touch-session" parameter to the session manager
(which wouldn't be a bad TC enhancement
> -Original Message-
> From: Adam Gordon [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 25, 2008 13:11
> To: Tomcat Users List
> Subject: Re: Session expiration and AJAX issues
>
> Martin-
>
> We are using Struts, however, version 1.2.9. But, after
&g
--- 10:10AM Mon 25 Feb 2008, Adam Gordon
<[EMAIL PROTECTED]> wrote:
> Storing the date/time a user logs in on
> the session is
> probably useful, but our problem is that we want to
> forcefully log the
> user out if there's no human present at the computer
> and the AJAX tasks
> keep a user's
: "Tomcat Users List"
Sent: Monday, February 25, 2008 11:04 AM
Subject: Session expiration and AJAX issues
A couple of issues:
We've set our session expiration to 12 hours (I know it's long) and
we're seeing behavior where certain browsers (namely IE) apparently
can'
Paul-
> Are you saying that certain browser will never expire their sessions?
> Or are you saying that certain browsers kill their sessions before 12
> hours (because they can't count that high)?
The former, i.e. that browsers will never expire the sessions.
> The way I understand it - you are
Hi,
> We've set our session expiration to 12 hours (I know it's long) and
> we're seeing behavior where certain browsers (namely IE) apparently
> can't count that high (we set the meta Refresh header but the page
> doesn't reload after the allotted time, session expiration time + 20
> minutes)
A couple of issues:
We've set our session expiration to 12 hours (I know it's long) and
we're seeing behavior where certain browsers (namely IE) apparently
can't count that high (we set the meta Refresh header but the page
doesn't reload after the allotted time, session expiration time + 20
m
11 matches
Mail list logo
