W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

[Bug 17264] New: Add attributes to use ping/pong frames effectively

From: <bugzilla@jessica.w3.org>
Date: Thu, 31 May 2012 06:10:56 +0000
To: public-webapps@w3.org
Message-ID: <bug-17264-2927@http.www.w3.org/Bugs/Public/>

           Summary: Add attributes to use ping/pong frames effectively
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebSocket API (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: toyoshim@chromium.org
         QAContact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org

How about adding new attributes to control ping/pong frames.

// ping-pong handling
attribute unsigned long pingInterval;
attribute unsigned long pongTimeout;

If pingInterval is specified, a browser will send ping frames in every
pingInterval msec.
If pongTimeout is specified, a browser will _fail_ the connection if any pong
is received in the last pongTimeout msec.

It's very important for some applications to know the server can not send some
critical event to the client
immediately. So to detect unstable network connection is very useful.
Of course, this feature can be implemented on the top of WebSocket connection
as a user level protocol.
But, it's effective to use RFC6455 defined ping/pong frames here.

Configure bugmail: https://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 Thursday, 31 May 2012 06:11:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:34 UTC