But today I always start with plain HTTP, then try SSE, and finally WebSockets if I have to.
For infrequent requests everything goes through the api, but for stuff like chat and live-document-editing, nodejs is the better solution.
But to answer this new question:
* You can have bidi without WS.
* Because WS is more complicated.
Because I was answering this question: "What's wrong with normal HTTP requests for client->server streams?"
> You can have bidi without WS.
Only by combining HTTP (which doesn't scale because my api server runs rails) and SSE (which does scale). If I want scaling bidirectional communication, I need websockets.
> Because WS is more complicated.
More complicated than SSE? I don't think so.
I guess I'm not seeing what the alternative setup would be, even with WebSockets.
You may be confusing it with HTTP/2 Push, where a server can inform a client of a future resource it will need, which is _de facto_ dead, with only a few real implementations beyond the bare minimum required by the HTTP/2 specification.
I think there's value in keeping our protocols as simple as possible to accomplish the task at hand.