louiscryan

3 ms·

1. 1.▲
   by louiscryan 12y ago

   Multiplexing RPCs onto a single WebSocket has some serious downsides. For one you now have an entirely custom protocol that standard proxies will not understand and cannot route. GRPC is very careful to be valid HTTP/2 for this reason.
2. 2.▲
   by louiscryan 12y ago

   This is an interesting an complex topic. Kenton does a pretty good job discussing this here https://capnproto.org/news/2014-06-17-capnproto-flatbuffers-... and rightly mostly focuses on the message-encoding aspects. Pe
3. 3.▲
   by louiscryan 12y ago

   Websocket does framing at the application layer, not the transport layer. Its probably more accurate to say that websocket lets you send binary or text messages. More specifically this means that multiple WebSockets are not multiplexed over
4. 4.▲
   by louiscryan 12y ago

   That is certainly a goal for Websocket-over-HTTP2, though in truth it would be no cheaper than long-poll-over-HTTP2 and more expensive if you invented your own metadata mechanism rather than using HTTP2 headers. And as you say, less idiomat
5. 5.▲
   by louiscryan 12y ago

   HTTP2 is superior to WebSocket at the transport layer because it adds explicit framing support and other things. Websocket-over-HTTP2 is coming, but it's not here now. While HTTP/1.1 was a poor transport for high-perf RPC there ar