Re: [fetch] Define the WebSocket client handshake in terms of Fetch (#236)

This looks much less painful than anticipated.

The need for "obtain a WebSocket connection" being overridden isn't completely clear. Why is step 1 omitted? And why is _resource name_ excluded?

> should Fetch abstract the entire WebSocket protocol or should HTML reference a mixture of Fetch and the WebSocket protocol? That is, should Fetch reintroduce the hooks HTML needs, perhaps even putting the security limitations on them directly so HTML no longer needs to do that. I think I have a slight preference for that, but it would be a larger change.

I'm not really clear what the difference would be, concretely, but in the abstract wrapping everything in fetch sounds a bit nicer. On the other hand, there are a lot of concepts in [WSP] referenced by HTML, and if these two are the only ones you need to override, then just having a no-op forwarding layer between Fetch and WSP would be a bit annoying.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/236#issuecomment-193394985