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

[Bug 13180] New: [Editorial] Causes that lead to failing the WebSocket connection, which results in an error event, should be more clearly specified

From: <bugzilla@jessica.w3.org>
Date: Thu, 07 Jul 2011 21:41:12 +0000
To: public-webapps@w3.org
Message-ID: <bug-13180-2927@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13180

           Summary: [Editorial] Causes that lead to failing the WebSocket
                    connection, which results in an error event, should be
                    more clearly specified
           Product: WebAppsWG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebSocket API (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: adrianba@microsoft.com
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org


The reasons for failing the WebSocket connection are spread throughout the
spec. It would be helpful to implementers to gather these together in a section
that describes the error event.

There are a limited number of cases where this occurs based on my reading:
* There is a failure to establish a websocket connection
* The connection is closed before it is opened
* The WebSocket is “disappeared” before it is opened

-- 
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 Thursday, 7 July 2011 21:41:17 GMT

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