Is Web2 Session management broken?

[Ivan_Tellez]

Documentation states on the Closing event of the WebSession:

@Documentation

A session begins to close automatically when the user navigates away from your app. This could be by navigating to another URL or by closing the tab or window. You can manually end a session by redirecting the user away from the app yourself using ShowURL. After the user navigates away, the session automatically closes when the UserTimeOut property value is reached. The default is 3 minutes. If the user returns to your app (via Back or re-entering the URL) before the timeout, then the session will still be available for use.

Well, this is NOT true. As Rick pointed out here: Web 2.0 App development, lifecycle and session management

At every refresh (or at every “via Back or re-entering the URL”) a new session id is generated, so is this a Documentation Bug and Xojo cant restore a session? or a Sofware Bug that should be fixed to allow the session to be restored?

And we are not talking about restoring all the GUI, just the same session Id (And its properties, like user loged in or the users items in a shopping cart even if not in, etc.) even if the user is redirected to a home page and the GUI rebuilt.

@Ricardo_Cruz

[Daniel_Mullins]

@Documentation

automatically when the user navigates away from your app. This could be by navigating to another URL or by closing the tab or window. You can manually end a session by redirecting the user away from the app yourself using ShowURL. After the user navigates away, the session automatically closes when the UserTimeOut property value is reached. The default is 3 minutes. If the user returns to your app (via Back or re-entering the URL) before the timeout, then the session will still be available for use.

Have you tried 2022r2 or r3, as it appears to be fixed there.

[Ivan_Tellez]

@Daniel_Mullins

Have you tried 2022r2 or r3, as it appears to be fixed there.

Im using 2022r2

[Daniel_Mullins]

You are right. I just tested both and it is not working.

[Ricardo_Cruz]

Yes, I definitely didn’t express that correctly. Since 2022r2, the browser will continue with its session in cases where the connection to the server has been interrupted temporary. As soon as the browser can connect again to the server, it will try to reuse the same session and continue where it was. For example, your device is switching to another Wifi.

It can also happen when the user switches to another iPhone app, the OS will likely suspend Safari. As soon as the user comes back to that browser and opens that tab (without reloading the page), the framework will do its best to recover the session.

If the session has expired, the browser will reload the page automatically and a new session will be created.

Every time the browser refreshes the page, a new session will be created. The previous one will expire eventually (3 minutes by default).

I hope that helps.

[Ivan_Tellez]

@Ricardo_Cruz

Every time the browser refreshes the page, a new session will be created. The previous one will expire eventually (3 minutes by default).

I hope that helps.

Ok thanks

By the way, the UserTimedOut event does Nothing right? No desconnection, no session ending, just a notification?

[Ricardo_Cruz]

Just a notification, yes, for example in chat application to show that user is away.