Am 05.08.2014 um 16:54 schrieb Klaus Berkling :
>
> On Aug 5, 2014, at 1:04 AM, René Bock wrote:
>
>> But my tests shows, that the WOSession.SessionDidTimeOutNotification is send
>> every time a session terminates – regardless if the session was timed out or
>> terminated explicitly
>> .
>>
On Aug 5, 2014, at 1:04 AM, René Bock wrote:
> But my tests shows, that the WOSession.SessionDidTimeOutNotification is send
> every time a session terminates – regardless if the session was timed out or
> terminated explicitly
> .
> Which is bad, as I only want to take an action on session tim
I have a similar requirement than Ted.
But my tests shows, that the WOSession.SessionDidTimeOutNotification is send
every time a session terminates – regardless if the session was timed out or
terminated explicitly
.
Which is bad, as I only want to take an action on session time out :-(
Am
If I am in my app, and a session was created, is there a method (that I can
override) that is called when the session terminates? Specifically, if the user
closes the window (does not log out), I want to do some cleanup before the
session disappears totally.
Ted
___
You can override WOSession.terminate() or listen for
WOSession.SessionDidTimeOutNotification.
Cheers,
- hugi
On 22.7.2014, at 15:26, Theodore Petrosky wrote:
> If I am in my app, and a session was created, is there a method (that I can
> override) that is called when the session terminates?
