on 6/19/01 2:06 AM, "Gareth Coltman" <[EMAIL PROTECTED]> wrote:
> Thanks for your lengthy reply jon. ;) but I don't understand how your
> suggestion is possible. I don't want to check if every session
> is old, but check on a per screen basis.
That is per request basis.
> Ie. If my screen contains data that
> is not persisted, and therefore requires it to be in
> the session, I must be able to check whether the session is fresh.
No, you should check if the data you need is there.
Note: you aren't using Pull at all.
> Otherwise,
> on pages with no data taken from the session I don't
> care whether the session has expired or not. I don't see how I could achieve
> this with a session validator.
The SessionValidator will tell you if the session exists or not. If not,
then show a session timed out screen by simply modifying the Parameter's in
the ParameterParser. That is what you originally asked for.
> I suppose I could have the sessionvalidator return false for
> requiresNewSession but I am worried about knock on effects in Turbine
> (my understanding of how Turbine handles sessions is fairly primitive as you
> can tell!)
Turbine's session handling is defined in the Servlet API. All we do is
provide hooks that allow you to modify the application state during
processing so that you can conditionally do things.
-jon
--
"Open source is not available to commercial companies."
-Steve Ballmer, CEO Microsoft
<http://www.suntimes.com/output/tech/cst-fin-micro01.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
