Project

General

Profile

Actions

Feature #3803

closed

Client keep-alive detection

Added by Drew Dormann about 9 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Benoit Daccache
Target version:
Start date:
02/17/2015
Due date:
% Done:

0%

Estimated time:

Description

The Doxygen page for Wt::WApplication mentions this:

keep-alive messages in the background will keep the session around as long as the user has the page opened

It would be valuable to be able to query the status of this keep-alive, from the client side.

A client browser could then perform appropriate Javascript action if network connectivity went down or the server went away or something similar. Similarly, an end-user could be given feedback to reflect that the current session really is "active" and not in a disconnected state.

Actions #1

Updated by Benoit Daccache over 8 years ago

  • Status changed from New to Closed

In the latest git version, a monitor has been implemented that allows a user to be notified of different events like connection closed, etc...

You can look at https://github.com/kdeforche/wt/blob/master/src/Wt/WApplication#L1052 for more information

Actions #2

Updated by Drew Dormann over 8 years ago

Very nice!

I was negligent in not providing an obvious use case, which would be familiar to the Wt crowd.

On Wt's own website http://www.webtoolkit.eu/, there is a persistant chat widget, which might display the text "Chat: guest 3 (3 users)"

If the network were then manually disconnected, the current behavior of the chat widget is to display "(3 users)" forever. With this feature, the message could potentially be updated to instead display "disconnected" or something similar.

Actions #3

Updated by Koen Deforche over 8 years ago

  • Status changed from Closed to InProgress
  • Assignee set to Benoit Daccache
  • Target version set to 3.3.5

Great idea!

Actions #4

Updated by Benoit Daccache over 8 years ago

  • Status changed from InProgress to Resolved
Actions #5

Updated by Koen Deforche over 8 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF