WebTransport: компромиссы

Question

Accepted Answer

WebTransport earns complexity for parallel streams и unreliable datagrams; SSE/WebSocket often enough; HTTP/3 end-to-end required.

## Разбор

- **Server→client only? SSE. Simple duplex? WebSocket fine.** WebTransport when **many parallel streams** or **unreliable datagrams** — games, live media, telemetry. Chat — overkill.
- **Support catch.** **HTTP/3 end-to-end** — CDN, LB, origin QUIC/h3; Safari lagged. 2026 viable but not universal default; WebSocket fallback common.
- **You build reconnection, auth, framing** — transport not framework. No free `Last-Event-ID` resume.
- **When NOT:** every browser/corporate proxy today, или single ordered channel enough.

## Итог

WebTransport for datagrams/multistream over h3; fallback and infra readiness matter; not chat-app default.