I understand that within a HTTP Session, we can have multiple connections (i.e. HTTP requests/responses). However, I'm wondering what the use case is for that. When we have multiple connections within 1 session, is it because we want to send all those HTTP requests at once? And if so, wouldn't it be better to separate the different HTTP connections into their own separate sessions for better modularity since it does the same thing?
Thanks for reading!
Hi Chee Yang
I believe the idea behind using multiple connections within a single session would be to pass data that is received by the first connection (such as cookies) onto the other connections in the session. The same handle is used for all connections defined in the session. I'm referring to the answers of the following question to give you more information HTTP protocol with multiple connections in one session. - DataMiner Dojo.
I'm not entirely sure if this is the main goal but I think it's still an advantage.