Pipelining and multiplexing in HTTP connection.
Yes, HTTP is that old. Same of my age. So today we were troubleshooting an issue and found that our application was consuming new TCP connection which led to SSL handshake between client and server communication while there was already open TCP connection with server. We are using HTTP 1.1 concurrent with pool numbers in which if a sequential call is not completed you cannot have another request until that call is completed default behavior of HTTP 1.1. So, i put my hat of research and wanted that same TCP should be used for the new call instead creating new one so i Google it and found the concept of Pipelining in HTTP 1.1, I thought yes i crack the thing and now we will implement it and will use same connection for all the streams but wait what HTTP 1.1 pipelining have same serious issue and one should use HTTP 2.0 instead but i then again hit by a surprise that HTTP 2.0 also have some issue and now there is a new version of H...