Preferences -> Advanced -> HTTP-Networking
i did search about this for short:
http://www.webmasterworld.com/forum21/8007-3-10.htm
http://www.peoplesrepublicofcork.com/~p … 19009.html
http://zgp.org/pipermail/linux-elitists … 07815.html
> What about browser.turbo.enabled?
Has to do with what is now called "quicklaunch" (and which doesn't work on
Linux; this pref isn't used anymore.) I learned this from THE FIRST Google
hit, BTW.
and about pipelining for surfing the web read this:
http://www.mozilla.org/projects/netlib/ … g-faq.html
for computer newbies: nice explanation about pipelining:
http://cse.stanford.edu/class/sophomore … ipelining/
->
normal:
pipelining:
:-)
]]>to get started, type about:config in the address bar, and press <enter>. then change the following keys as indicated:
1. browser.turbo.enabled - true (FF MOZ)
2. network.http.pipelining - true (FF MOZ)
3. network.http.pipelining.firstrequest - true (FF)
4. network.http.pipelining.maxrequests - 32 (FF MOZ)
5. network.http.proxy.pipelining - true (FF MOZ)
6. nglayout.initialpaint.delay - 0 (FF)
Enabling the pipelining features allows the browser to make multiple requests to the server at the same time. The "maxrequests" is the maximum number of requests it will send at once. I've heard that 8 is the most it will send at once, but setting it higher won't hurt, just in case. The initialpaint.delay is the length of time (in milliseconds) after the server response before the browser begins to paint the page.
with those settings, most people report a noticeable speed boost in rendering pages. YMMV.
have fun!
]]>