[Seaside] Re: Handling expired Session in Seaside 3.0

Udo Schneider udo.schneider at homeaddress.de
Wed Nov 3 19:56:27 UTC 2010


Thanks for the pointer to WAApplication#handleExpired:. I'll take a look 
at it.



On 03.11.10 08:35, Johan Brichau wrote:
> Udo,
> As far as I know, you would need to create a specific subclass of WAApplication and override #handleExpired: to do what you want.
> Then use that specific subclass to register your main component as an application (the standard WAAdmin>>register:asApplicationAt: uses WAApplication)
> Overriding #initialRequest: on your initial component might be of help to know if the request was for an expired session. But you probably need to pass some info in the request in the #handleExpired: method.
> Now, this is all theory, I have no experience doing that myself ;-)
> Let us know if you succeed.
> Johan
> On 02 Nov 2010, at 21:41, Udo Schneider wrote:
>> All,
>> if this is just an RTFM question I'm happy to read on my own ... however I'm searching for a solution to handle expired sessions in Seaside 3.0. My goal is to either display a specific component when a request for an expired session is recieved or to be able to find out if a request was for an expired session in my initial component.
>> Any pointers?
>> CU,
>> Udo
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list