[Seaside] unregistered not called on expired session?

[Bernhard Pieber]

Hi David,

Thank you for your answer. I understand better now how it was designed.

Bernhard 

> Am 11.03.2018 um 15:14 schrieb David Tibbe <david at tibbe.info>:
> 
> Hi Bernhard,
> 
> remember, #unregistered is not getting called when the expiry occurs.
> There is no background thread checking all session if they are expired.
> 
> Instead, when creating a new session, the current cache is getting
> checked for old entries and if found, they're getting removed and by
> that, the #unregistered is getting called.
> 
> Just put a breakpoint in it, wait for the expiry and create a new
> session, then the debugger should pop up and you can follow the call flow.
> 
> BR,
>  David
> 
> Am 10.03.2018 um 17:40 schrieb Bernhard Pieber:
>> Hi all,
>> 
>> I have registered my own session class and I want to run some code when the session expires. I overwrote unregistered, writing to the Transcript and calling super unregistered.
>> 
>> When I click on New Session in the toolbar I see it in the transcript. However, when the session expires because there is no activity nothing is written to the transcript.
>> 
>> I set both Maximum Absolute Age and Maximum Relative Age to 10 seconds in the config application. I know the sessions are expired because they are no longer returned when calling WAApplication>>#sessions.
>> 
>> Is this a bug, or do I misunderstand something?
>> 
>> I am using Seaside 3.2.2 on Pharo 6.
>> 
>> Bernhard
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>> 
> 
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside