On Fri, 10 Oct 2008, Wellington Fernando de Macedo wrote:
Some questions has been raised since the comment #75
(https://bugzilla.mozilla.org/show_bug.cgi?id=338583#c75). We would like
to know what exactly mean cause the user agent to stop trying to
process this event source. The current
Ian Hickson wrote:
It just means do nothing (including not automatically retrying). If the
event source is reregistered, then it should go through the same process
again; the error response doesn't block that URL for all time.
So in practice until page reload, right?
Why are DNS errors
On Fri, 10 Oct 2008, Boris Zbarsky wrote:
Ian Hickson wrote:
It just means do nothing (including not automatically retrying). If the
event source is reregistered, then it should go through the same process
again; the error response doesn't block that URL for all time.
So in practice
Ian Hickson wrote:
So in practice until page reload, right?
Or until the URL is added in another eventsource element, or
addEventSource(), with the same URL, sure.
OK.
Why are DNS errors different from under underlying network layer errors
here?
The intent is for DNS and HTTP 4xx
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
