W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

[Bug 13104] 1) ping(msg); //allow client to send server ping as per websocket spec 2) onpong(); //allow client to receive response of ping

From: <bugzilla@jessica.w3.org>
Date: Mon, 12 Sep 2011 19:00:01 +0000
To: public-webapps@w3.org
Message-Id: <E1R3Bjd-0003F7-FJ@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13104

Iņaki Baz Castillo <ibc@aliax.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |ibc@aliax.net
         Resolution|NEEDSINFO                   |

--- Comment #3 from Iņaki Baz Castillo <ibc@aliax.net> 2011-09-12 19:00:00 UTC ---
(In reply to comment #2)
> What's the use case?

In case the network connection goes down (for example the ADSL dies), the
WebSocket client could not realize of it until it attempts to send a new WS
frame (it happens sometimes because there is not a TCP disconnection).

By sending periodical WS Ping frames from client to server, the client could
realize of the network issue in a reasonable time.

As a suggestion, the WS API could include an interval for sending Ping frames
to the server:

    var myWebSocket = new WebSocket("ws://some-domain.com");
    myWebSocket.set_monitor_interval(120);

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 12 September 2011 19:00:14 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT