Re:The future of web software is HTML over WebSockets
by viklove on Friday February 26, 2021 @04:55PM
(#26280315)
I can, but why would I limit myself to one-way communication when I can have bidirectional communication?
[ Parent
| on HN ]
Re:The future of web software is HTML over WebSockets
by anderspitman on Friday February 26, 2021 @06:39PM
(#26281159)
You didn't cite bidi as your reason for choosing WS in your last comment, you cited scaling and node vs ruby.
But to answer this new question:
* You can have bidi without WS.
* Because WS is more complicated.
Re:The future of web software is HTML over WebSockets
by viklove on Monday March 01, 2021 @01:04PM
(#26305836)
> You didn't cite bidi as your reason for choosing WS in your last comment, you cited scaling and node vs ruby.
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.