Isn't the behavior still the same in either case? If the session times out
with the current code you get redirected, if it times out with the change
you just get a different screen then what you requested. In either case you
still loose your session and don't get back to where you were before.
----- Original Message -----
From: John McNally <[EMAIL PROTECTED]>
To: Turbine <[EMAIL PROTECTED]>
Sent: Friday, January 21, 2000 12:58 PM
Subject: Re: Clarification on session init
> > Am I missing something important here or is this an acceptable
> > optimization? I've tested it and to me it looks like you get the same
> > behaviour but without the extra redirect. What am I missing?
> >
>
> I'm not sure there is anything wrong with changing this, but examine the
> consequences of this possibility. A user has walked away for some time
and
> their session has timed out. Turbine therefore sends them back to the
> homepage (Login). The user then submits next request, still using the old
> session id. I don't have time to examine the consequences, but it would
> seem at the very least that they may be redirected at this point, which
> would be annoying since they entered some info and the system could have
> told them earlier. Again, maybe there is no problem, as long as
> SessionValidator is setup properly. Sorry I do not have time to help
sort
> through this.
>
> John McNally
>
>
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
