09-18-2019, 04:57 PM
09-23-2019, 09:26 AM
The only thing that actually destroys a session is the timeout thread, even when you explicitly terminate a session (it will be collected later by the timeout thread in the background).
I wonder if you are trying to find out is if a timeout actually occurred?
I wonder if you are trying to find out is if a timeout actually occurred?
09-23-2019, 10:02 AM
Hallo Alexander,
when the user clicks a 'close' button on the main form, my application is terminated by source line:
WebApplication.Terminate('Sessione conclusa.');
So I see that "IWUserSessionBaseDestroy" is immediately activated.
This is the reason to know if the destrroy derives from a regular close or from system timeout.
Do I wrong anything?
Thank you very much for your time.
when the user clicks a 'close' button on the main form, my application is terminated by source line:
WebApplication.Terminate('Sessione conclusa.');
So I see that "IWUserSessionBaseDestroy" is immediately activated.
This is the reason to know if the destrroy derives from a regular close or from system timeout.
Do I wrong anything?
Thank you very much for your time.
09-24-2019, 03:08 PM
If there isnt anything built in, you could always set a flag on the session when you terminate it manually.
09-25-2019, 06:46 AM
(09-24-2019, 03:08 PM)kudzu Wrote: [ -> ]If there isnt anything built in, you could always set a flag on the session when you terminate it manually.Thank you very much. I will do so.