Connection Multiplexing is most valuable for which HTTP version?
Connection Multiplexing is most valuable when client behavior would otherwise create many short-lived server-side TCP connections. HTTP/1.0 is the best fit for this benefit because HTTP/1.0 commonly opens a separate TCP connection for each request unless keepalive behavior is specifically used. Avi Connection Multiplexing decouples the client-side connection from the server-side connection and allows the Service Engine to reuse server-side TCP connections for multiple HTTP requests. This reduces connection setup and teardown load on backend servers. HTTP/1.1 already introduced persistent connections as a standard behavior, so the relative benefit is smaller than with HTTP/1.0. HTTP/2 has its own multiplexing model at the protocol level. Therefore, Connection Multiplexing is most valuable for HTTP v1.0.
Currently there are no comments in this discussion, be the first to comment!