Add new transport: gRPC-Web about engine.io HOT 2 OPEN

@darrachequesne when I read up more on this, I am not confident gRPC-Web is suitable for socket.io - at least not yet. It seems to require a proxy (Envoy). It is currently also only good for server streaming, not client streaming. So maybe close this issue and re-open in the future?

Regarding HTTP/2 (gRPC) vs WebTransport (UDP), only some future performance measurements could solve that. What I believe is that the gRPC serialization packs more information than e.g. JSON, hence less data, hence more performant. But do not take my word for it: I do not know.

from engine.io.

That's an interesting idea, thanks for the heads-up 👍

WebTransport is an alternative, but gRPC-Web might arguably be more performant.

Do you have any source for that claim? Given that gRPC is built on HTTP/2 (TCP), I would have thought that WebTransport (based on UDP) would be more performant.

References:

• https://cloud.google.com/blog/products/api-management/understanding-grpc-openapi-and-rest-and-when-to-use-them?hl=en
• https://www.infoq.com/articles/websocket-and-http2-coexist/
• https://grpc.io/about/

from engine.io.