3 ms·
That seems mostly like the question of "Does this HTTP framework support HTTP pipelining". While I don't know the answer, it doesn't seem highly relevant. Most
by Matthias247 5y ago
That seems mostly like the question of "Does this HTTP framework support HTTP pipelining". While I don't know the answer, it doesn't seem highly relevant. Most clients went away from using pipelining, since follow-up requests on the same connection are subject to unknown latency (stuck behind the first request) and a connection failure can impact all of those requests.
The better approach is to use either more connections, or proper request multiplexing via HTTP/2 or /3. In the latter case a server framework would just see multiple request invocations in parallel.
- polynox 5y ago> subject to unknown latency (stuck behind the first request) Also known as "head of line blocking" https://en.wikipedia.org/wiki/Head-of-line_blocking https://en.wikipedia.org/wiki/Head-of-line_blocking
- jrochkind1 5y agoNo, that's a different thing. HTTP request 2 from this scenario is from an entirely different client on an entirely different socket connection. (This kind of architecture might also be useful for http pipelining, but that's not the question in this scenario)