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

[websockets] Reintroducing onerror

From: Adrian Bateman <adrianba@microsoft.com>
Date: Tue, 7 Jun 2011 14:40:30 +0000
To: "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>
Message-ID: <104E6B5B6535E849970CDFBB1C5216EB4334A74A@TK5EX14MBXC136.redmond.corp.microsoft.com>
This check-in [1] reintroduces the onerror handler that was removed previously [2].
Since, in general, WebSocket protocol errors are fatal and result in onclose, what is
the purpose of adding this back? We have removed onerror from our implementation
since the previous change and it's frustrating trying track against the spec with
unexpected updates.



[1] http://dev.w3.org/cvsweb/html5/websockets/Overview.html.diff?r1=1.221;r2=1.222;f=h
[2] http://dev.w3.org/cvsweb/html5/websockets/Overview.html.diff?r1=1.215;r2=1.216;f=h
Received on Tuesday, 7 June 2011 14:41:30 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:32 UTC