• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

persisten connection

rookie1010

Senior member
Hello,

I was wondering why a client would require more than one persistent connection. Can not all requests to the server be handled by a single persistent connection.

When a server is handling multiple multiple http connections, are all the requests destined for the same port, i.e. port 80 or port 8080?
 
Initially HTTP was stateless, meaning that each request was issued on a separate connection. I believe HTTP 1.1 adds the ability to make multiple requests in the same connection but it's still limited to a certain number of requests so that one client can't tie up resources on the server by just leaving a connection open.

When a server is handling multiple multiple http connections, are all the requests destined for the same port, i.e. port 80 or port 8080?

Yes, the webserver only listens on the few (usually 80 and maybe 443) ports that you tell it so any incoming connection has to be on those ports.
 
thanks for the reply, so since there is an upper limit to the number of requests in a single persistent connection, hence multiple persistent connections are alowed, correct?
 
Probably, I don't know for sure off the top of my head but I would guess that it's also configurable on the webserver.
 
Back
Top