[Seaside] How to deal with expired sessions on Ajax callbacks

Boris Popov boris at deepcovelabs.com
Fri Nov 2 17:57:09 UTC 2007

SUAjax>>onExpiry: anObject
 self onStatus: 403 do: anObject

(html updater)
 onExpiry: html javascript refresh;

I also overrode #evaluator, #periodical, #request and #updater on my
render canvas class to set default handlers for expiry and errors so I
wouldn't have to specify them every time.

Hope this helps,



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

boris at deepcovelabs.com


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

Thank you.

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Alexandre Paes
> Sent: Friday, November 02, 2007 10:50 AM
> To: Seaside - general discussion
> Subject: [Seaside] How to deal with expired sessions on Ajax callbacks
> Hi seasiders,
> Does anyone have any process of dealing with expired sessions on Ajax
> callbacks? This is very annoying when the session expires but the
> application is still open on the browser, the client is left without
> functionality and without any insight into why the application is not
> responding.
> Cheers,
> Alex Paes
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list