[whatwg] HTML5 - Server-Sent Events Implementation for Mozilla
ian at hixie.ch
Fri Oct 10 15:32:48 PDT 2008
On Fri, 10 Oct 2008, Boris Zbarsky wrote:
> > The intent is for DNS and HTTP 4xx (except auth errors) or 5xx errors
> > to be treated the same way. I'll try to make the spec clearer about
> > this.
> I guess the real question is whether it should be treated differently
> from, say, a socket-level error (e.g. "no network interface is up", "no
> route to host", etc, etc). Seems to me like it shouldn't.
> Basically, the current proposed Gecko patch treats DNS failure
> specifically differently from the other possible error status codes
> (socket errors, out of memory errors, user pressing the stop button,
> etc, etc). If feel like we should treat all such failures (and non-2xx
> HTTP responses, since this is the level above the HTTP impl and hence
> never sees 3xx responses unless redirection failed) identically.
> Does that make sense?
Yes, that was the intent of the current spec. I'll try to clarify it when
I next work on this section.
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg