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

> The need for "obtain a WebSocket connection" being overridden isn't completely clear.

Note that "establish a WebSocket connection" in the RFC is the process of obtaining a connection, coupled with sending a request and validating the response. It's all things intertwined.

> Why is step 1 omitted? And why is resource name excluded?

Step 1 is omitted because we already validated the input. Resource name is not actually used to obtain a connection. It's used for the handshake that is separately overridden (the larger section with all the header appending).

> 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.

I think I would import some of the subsetting that HTML does around error handling. But yes, there will be some forwarding too.

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