Re: [whatwg/fetch] Consider adding load balancing / failover to Fetch? (#775)

As noted, expressing this via `SRV` is undesirable for a host of reasons - most notably, in practice, it does not work with any degree of fidelity from clients. This is something that Chrome has "strong negative signals" - we've closed those feature requests as WontFix rather intentionally.

In general, the cost of making something "generally useful" is to introduce a host of other concerns. I would think a very clear explainer doc explaining the use cases beyond NEL should be written before having more concrete discussions on this, in order to guide the discussions and the priorities. The state machines that implementations and developers need to maintain to effectively handle this client-side would be quite complex (for both parties), and it is not clear that users would concretely benefit from this - indeed, if the edge cases are ample enough, the user experience may be actively harmed in the aggregate.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/775#issuecomment-403218488