"quote"

1. Type "about:config" into the address bar and hit return. Scroll down and look for the following entries:

network.http.pipelining
network.http.proxy.pipelining
network.http.pipelining.maxrequests

Normally the browser will make one request to a web page at a time. When you enable pipelining it will make several at once, which really speeds up page loading.

2. Alter the entries as follows: (by double clicking them)

Set "network.http.pipelining" to "true"

Set "network.http.proxy.pipelining" to "true"

Set "network.http.pipelining.maxrequests" to some number like 30. This means it will make 30 requests at once.

3. Lastly right-click anywhere and select New-> Integer. Name it "nglayout.initialpaint.delay" and set its value to "0". This value is the amount of time the browser waits before it acts on information it recieves.
"end quote"

found this on Gamefaqs so might as well share it.
http://boards.gamefaqs.com/gfaqs/genmessage.php?board=2000112&topic=18126452

But do note:
"From: jwsin | Posted: 1/8/2005 5:36:25 PM | Message Detail
if too many ppl do this it will start flooding servers you SHOULD NOT SET THE NUMBER OF CONNECTIONS TO 30!!!!

that is just too many 5 is reasonable. by setting it to thirty you take up thirty connections and if 5 of you guys try to access a site that can only hold 90 two of you are screwed"

I'll explain to you why webmasters hate "download accelerators" just like this.

HTTP servers allow only so many connections at once. Sure its possible to bump the number up, however the more connections you configure as the maximum you'll allow determines just how much resources the webserver chews, and when you've reach the threshold of maximum connections and machine load, it means having to get new/more hardware, or be ignorant enough to deal with people complaining that your server is inaccessable.

Here is the dilemma. Users that open more connections chew more resources short term, but the quicker they release the connections they use, the quicker they are freed for other users to utilise them. However users comply to the (2 maximum connections at a time between a client and server) rule, more users can be accessing data in the short term, but it takes longer for their 2 "slots" to free up.

Of course its more than possible for users who dont use download accelerators to eat your webserver and bandiwdth for a light snack... one such phenomenom is called "the slashdot effect".

This isn't about increasing the number of connections, though,it's utilizing the ones you have more efficiently. Pipelining lets the browser queue up several requests over a single persistent HTTP connection. This lets the web server start processing the next request before the old one has finished transfering, thus freeing up the connection quicker. The "maxrequests" is not the number of HTTP connections to open, it's the number of requests to transmit over the single open connection.

ma bad.

Neat! So its OK then to set the pipeline to 30? Or how much do you guys here perefer?

>>5
from what i've read, the maximum firefox will do is 8, so setting it to 30 has the same effect as setting it to 8... the default value of 4 works just fine, so i left mine set at that.