Who is talking about limiting to one technology?

I'm saying websockets are not fit to purpose and I can't see a compelling reason to ever reach for that particular technology any more than I'd reach for COBOL. Sadly, the browser environment gives us very few choices for streaming data connections.

Really though, I suppose I am limiting to a single technology: HTTP. Which kind of makes sense, I am putting hypertext content in a hypertext client over the hypertext transport protocol. If browsers spoke SSH, maybe I'd use that instead. I can't see a use case where adding a second protocol to my apps justifies the large increase in complexity when the capabilities are already better provided by the protocol that I'm already using.