Using updater on expired sessions?

Hmm, if you use a scriptaculous updater to refresh contents of a given 'div'
after your session expires, the new contents will include a brand new copy
of the application's home page :) Workarounds, anyone?

Cheers!

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> Hmm, if you use a scriptaculous updater to refresh contents of a given 'div'
> after your session expires, the new contents will include a brand new copy
> of the application's home page :)

That can be fixed, but I am not sure what should happen in case of a time-out.

> Workarounds, anyone?

Put a periodical updater into the page that calls the server every
couple of minutes. This should avoid the session to time-out as long
as the browser window is open.

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

I haven't looked at scriptaculous documentation yet, but wouldn't timeouts
trigger the onError handler?

And keeping the page from expiring isn't really an option in my case. This
is a financial application and we're intentionally keeping the inactivity
period very low before the expiry kicks in. What I think I may do for now,
is validate the contents of the div in the onSuccess and bail out of the
whole page if its not tagged properly. If you can think of a better way,
please share as it seems like this would be a typical scenario for a lot of
developers out there.

Keep up the good work!

Cheers!

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Lukas
Renggli
Sent: Friday, June 30, 2006 12:00 AM
To: The Squeak Enterprise Aubergines Server - general discussion.
Subject: Re: [Seaside] Using updater on expired sessions?

> Hmm, if you use a scriptaculous updater to refresh contents of a given
'div'
> after your session expires, the new contents will include a brand new copy
> of the application's home page :)

That can be fixed, but I am not sure what should happen in case of a
time-out.

> Workarounds, anyone?

Put a periodical updater into the page that calls the server every
couple of minutes. This should avoid the session to time-out as long
as the browser window is open.

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> I haven't looked at scriptaculous documentation yet, but wouldn't timeouts
> trigger the onError handler?

No, not at the moment, because Seaside redirects requests to sessions
that timed out to the root of the application and this causes your
particular problem.

Triggering the onError handler would be a good solution: I do so for
XMLHttpRequest in Seaside2.6b1-lr.51 and it nicely solves the problem.
Thanks for contributing this idea. Note that this problem is not
related to script.aculo.us but to Seaside, so I only needed to change
this package.

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

That'd be great, thanks Lukas.

Cheers!

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Lukas
Renggli
Sent: Friday, June 30, 2006 9:34 AM
To: The Squeak Enterprise Aubergines Server - general discussion.
Subject: Re: RE: [Seaside] Using updater on expired sessions?

> I haven't looked at scriptaculous documentation yet, but wouldn't timeouts
> trigger the onError handler?

No, not at the moment, because Seaside redirects requests to sessions
that timed out to the root of the application and this causes your
particular problem.

Triggering the onError handler would be a good solution: I do so for
XMLHttpRequest in Seaside2.6b1-lr.51 and it nicely solves the problem.
Thanks for contributing this idea. Note that this problem is not
related to script.aculo.us but to Seaside, so I only needed to change
this package.

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside