3 ms·

This can't be true, can it? I was under the impression that HTTP/2 used a persistent connection w/ multiplexing. This seems like it would be very nice in a web

This can't be true, can it? I was under the impression that HTTP/2 used a persistent connection w/ multiplexing. This seems like it would be very nice in a web-browser to front-end situation, but what about for internal service calls? Seems like persistent connection between services would mess w/ common load balancing schemes.

bastawhiz 8y ago
There's nothing stopping you from having one connection per request with HTTP/2. You could build your software to simply have the same behavior as HTTP/1.1 with keep-alive