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? Thanks, Adrian.