Transport

[mikedilger]

Numerous people have complained about websockets. I don't think the complaints are particularly significant or valid, but here are what people have suggested

• HTTP REST API
• HTTP/2 used bidirectionally
• WebTransport (this is Websockets upgraded to work over QUIC)

Going back to a REST API is IMHO dumb. It then requires polling since it would dump pubsub.

HTTP/2 is not really a replacement for Websockets despite the fact that you can sort-of misuse it (if you abuse the lower layers) to construct your own sort of bidirectional multiplexed websocket system. It would in particular not allow binary data because javascript has no API into that, so in that sense it would be a step backwards.

I think WebTransport is an aspirational ideal, solves every problem and then some, but because it isn't widely deployed and supported the world is not ready for it yet.

At the moment, therefore, I am in favor of sticking to websockets, but if WebTransport deploys rapidly I could be convinced to move to that.