How to keep session alive when my app is not user's current tab
Added by Jason D about 3 years ago
Hi,
I'm working on an app that needs to end the user session as soon as page/tab is closed. For this, I've set timeout to 2 seconds. But I still want the session to be kept alive when my page is open though not focused as current tab. Is there a way to achieve? Thanks in advance!
Best Regards,
Jason
Replies (4)
RE: How to keep session alive when my app is not user's current tab - Added by L K almost 3 years ago
I would be also very happy to know how to do it in chrome. Is there a way WT can keep such a session alive ?
RE: How to keep session alive when my app is not user's current tab - Added by Mark Travis almost 3 years ago
I'll put a "me, too" out here. As a matter of fact, I want to be able to keep a background process to the tab running a complex calculation until completion. It doesn't have to update the tab until it regains focus.
RE: How to keep session alive when my app is not user's current tab - Added by L K over 2 years ago
In my case its downloading a file where everyone changes the tab instead of waiting 10 minutes or longer. As far as I know it's browser dependent how it manages tabs and I dont have much hope WT can do sth. about it. But maybe I learn sth. new :)
RE: How to keep session alive when my app is not user's current tab - Added by Bruce Toll over 2 years ago
There is information that may be relevant in issue #8136. Also, possibly related: Websockets and long-polling seem unaffected by chromium t....