You can return (STOP) at the onSessionExpiringEvent
to keep the session alive. Now if you have to extend the session time
only on those specific pages then you would have to some how know from
which page the onSessionExpiringEvent is fired and conditionally
return(STOP).
If you have ND 4.1.3, you would have to use service pack 1 for ND 4.1.3
and run the PE Service out of process with '-nojit' option in order
to keep PE crashing from onSessionExpiringEvent.
Vishal
"Troy Mckinnon" <[EMAIL PROTECTED]> wrote:
>Hey all,
>
>has anyone come up with a solution to this problem yet.
>
>I am having a lot of trouble with it. A few of our pages have a lot of
>information required. It takes some users a lot of time to enter... (we
>timeout a lot) The timeout is already set to 30 minutes and I don't want to
>go any higher.
>
>I have SAVE SESSION buttons on the page, but I am required to make it happen
>automatically.
>Is there any way to use this event (sessionExpiring) without crashing it??
>
>Is there an ONBeforeSessionExpiry or something?
>
>I would really appreciate some help - I am getting desperate :)
>
>I am attempting to implement a javascript timer that will force a
>load(false) at 29 minutes... to ensure the session is kept active... (this
>will be nice if I getting working because Sessions are only kept alive if
>the browser is open)
>I still don't know if this is possible and if it is I would still like to be
>able to have a java fallback if javascript is disabled or whatever.
>
>Cheers
>
>Troy
>
>Troy McKinnon
>Technical Team Leader
>Integrated Quality Management System
>Nortel Networks - GHCT (Dept. 1J11)
>(613) 765-7685 or ESN (395) 7685
>
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
