Bypassing the browser restrictions on the number of connections
A few days ago, this video entry posted on metacafe was highlighted on digg . It explained how to increase the speed of opening sites by fine tuning the browser and changing its settings, which are responsible for the number of parallel connections. To explain why this works, let's get a little deeper into how browsers serve server connections.
Utilitarian choice
When developing any applications, all developers have to do what is called the “utilitarian” choice ( utilitarian choice ). If Jeremy Bentham is somewhat fussy to rephrase, then the “utilitarian” approach can be called “as a result of which we get the greatest amount of good for the largest number of [people]”. Many times, performance has been sacrificed for a small number of users so that, as a result, the average performance for all users in the aggregate would be better. ')
Browsers were created in an era when a huge number of users used dial-up access with low channel bandwidth, so it was then important to limit users to a small number of simultaneous connections. The overhead of switching between multiple connections with dial-up access made it very difficult to process and load each individual request. In addition, in that era, web and proxy servers were not powerful enough to support multiple connections, so such a hard limit on the number of simultaneous connections of the browser significantly reduced the risk of a drop in the network infrastructure as a whole.