Multiplexing is beneficial, otherwise we'd never have seen HTTP user agents opening up multiple TCP connections. The gain of moving to binary was the ability to multiplex multiple requests is a single TCP connection. It…
This depends on how the proxy is configured to behave. One common pattern is to have a protocol terminating proxy talk to the client. Other component(s) sit behind this and they could be other parts of the system, tiers…
There is still a place for WebSockets in HTTP/2. The fairly recent RFC 8441 defines a mechanism to reserve a single HTTP/2 stream for bidirectional WebSockets. It is feasible for a similar mechanism for also work for…
Do you mean forward proxies? The HTTP/3 draft currently specifies how the CONNECT method is used. At present, it only allows you to create an onward TCP connection. So you have a QUIC connection between client and…
Multiplexing is beneficial, otherwise we'd never have seen HTTP user agents opening up multiple TCP connections. The gain of moving to binary was the ability to multiplex multiple requests is a single TCP connection. It…
This depends on how the proxy is configured to behave. One common pattern is to have a protocol terminating proxy talk to the client. Other component(s) sit behind this and they could be other parts of the system, tiers…
There is still a place for WebSockets in HTTP/2. The fairly recent RFC 8441 defines a mechanism to reserve a single HTTP/2 stream for bidirectional WebSockets. It is feasible for a similar mechanism for also work for…
Do you mean forward proxies? The HTTP/3 draft currently specifies how the CONNECT method is used. At present, it only allows you to create an onward TCP connection. So you have a QUIC connection between client and…