Opened 16 years ago
Closed 15 years ago
#847 closed defect (duplicate)
Manage properly the timeout in the bassic weblayout
Reported by: | msuing | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | AJAX Viewer | Version: | 2.0.1 |
Severity: | minor | Keywords: | timeout |
Cc: | External ID: |
Description
When the user has reached the timeout in the ajax viewer, there is no error displayed warning him that the session has expired and suggesting him to reload the viewer.
This implies sometimes an error when the viewer is integrated into another application.
Change History (3)
comment:1 by , 16 years ago
comment:3 by , 15 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Addressed with RFC66 (#1026)
Note:
See TracTickets
for help on using tickets.
Have you managed this already?
I imagine that there are multiple points where the viewer interacts with the server. Each of those points would have to be wrapped to allow detection of an expired session.
I use a "ping" method for keeping the session alive, as long as the map is loaded. IT increases load slightly, if there are many idle users.