Quote:
Originally Posted by raymor
In most cases, two connections to
the server will max out your internet connection, or nearly so, so there is no
advantage at all to more connections. You'll only manage to be a dick head
holding open a bunch of connections slowly trickling data to your browser,
get broken images, and have to wait for the whole page to load before you
see even the first image at the top of the page appear.
|
I realise you probably quoted this from somewhere else, but frankly, it is wrong.
Quote:
In most cases, two connections to
the server will max out your internet connection, or nearly so, so there is no
advantage at all to more connections.
|
Rubbish. Pages should load in < 1 second over any decent "maxed out" connection. That's obviously not the case.
Quote:
You'll only manage to be a dick head
holding open a bunch of connections slowly trickling data to your browser.
|
Again, chances are the bottleneck lies somewhere other than your computer... unless you've gone completely over the top with concurrent connections or use an underperforming browser.
Presumably this means the connection has timed out. If not, you have bigger problems. Otherwise, you've gone nuts with way too many connections, your internet sucks, or most likely of all, the remote server is choking or blocking you.
Quote:
have to wait for the whole page to load before you
see even the first image at the top of the page appear.
|
Once again, the chances are this isn't an issue of concurrency. These delays are attributable to the browser's rendering behavior, as noted in instruction #3; "This value is the amount of time the browser waits before it acts on information it recieves."