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

RE: [websockets] Reintroducing onerror

From: Adrian Bateman <adrianba@microsoft.com>
Date: Wed, 8 Jun 2011 17:52:05 +0000
To: Ian Hickson <ian@hixie.ch>
CC: "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>
Message-ID: <104E6B5B6535E849970CDFBB1C5216EB43353007@TK5EX14MBXC136.redmond.corp.microsoft.com>
On Tuesday, June 07, 2011 10:36 AM, Ian Hickson wrote:
> On Tue, 7 Jun 2011, Adrian Bateman wrote:
> > 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?
> Ian asked me to put it back so that authors can distinguish between a 
> server closure and a client-initiated error-driven closure.

What is the difference between these two cases? When would onerror fire
that wouldn't result in onclose with wasClean=false? Isn't the wasClean
flag sufficient?


Received on Wednesday, 8 June 2011 17:52:35 UTC

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