[Bug 28823] Course of action even after Event Source retry failure.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28823

--- Comment #2 from Prashant Hiremath <hiremathprashants@gmail.com> ---
(In reply to Anne from comment #1)
> "Optionally, wait some more. In particular, if the previous attempt failed,
> then user agents might introduce an exponential backoff delay to avoid
> overloading a potentially already overloaded server. Alternatively, if the
> operating system has reported that there is no network connectivity, user
> agents might wait for the operating system to announce that the network
> connection has returned before retrying." is pretty clear, no?

Hi Anne, thanks for the reply.
Please correct my understanding -

In the example what I have mentioned it is particularly about DNS resolution
failure. As per the spec "Network errors that prevents the connection from
being established in the first place (e.g. DNS errors), must cause the user
agent to reestablish the connection in parallel."

And Now we will try to reestablish the connection and spec says "Alternatively,
if the operating system has reported that there is no network connectivity,
user agents might wait for the operating system to announce that the network
connection has returned before retrying."

But this is a case of "Name Resolution failure", not about N/W connectivity
problem as given URL(http://www.test.not) itself is invalid even though N/W
connection exists. So my bug report was particular about this kind of
scenarios, where N/W connectivity exists but reason for retry may be other N/W
related errors, how to handle this?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 17 June 2015 15:36:18 UTC