I don't care i know, i hate the guts of the software, but im here to help now.
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:
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.
If you're using a broadband connection you'll load pages MUCH faster now!
(yes there is fasterfox, but this with the extension works great..from what I hear not personal experiance i don't use firefox)
Well.
I once installed firefox, and lemme tell you like others asked, firefox gave me a virus, not anything i downloaded.
firefox itself.
and urm...i use i.e whatever you guys think, because i think its the best,
and im not even saying firefox sux.
AND
for those of you who use firefox a new version has released i heard.
Quote from: Nightwolf on November 15, 2006, 02:49:35 PM
and urm...i use i.e whatever you guys think, because i think its the best,
AND
for those of you who use firefox a new version has released i heard.
Once again I will say, don't use IE right out of the box, please take around 2 min's, to use my config to harden it. FIrefox is safer out of the box, but with some work IE can be the same.
Yes, it was relased a few weeks ago i thinkk.
Interesting... Firefox has pipelining... Didn't know that.
yey! it worked! will there be some disadvantages from doing this?
None that I know of...then again I don't use firefox, I can't seem to think of anything that could happen.
Pipelining pisses off owners of servers and busy websites, as the performance gain is alot more minimal than you think for the client, while it's a whole lot more load for the server. Alot of server owners who know what they're doing use counter measures to make their servers ignore pipelined requests (only one request at a time will be graced with a response), while some will go further and make things slower than even just using one connection for pipeliners.
I basically don't care right now, my own server is underused alot and it's load has never gone above even 0.1, so i forget about it.
But yeah, some builds of apache have pipelining disabled by default. Especially windows builds, seeing as on windows apache will open a seperate process for each connection (you have 7 people connected to your site, you'll have 8 apache.exes (7 hosts plus 1 master) running.
Thank you very much for the information! Wow! My already fast internet has just got faster! Woo Hoo!
finnaly a good comment...thanks I found it on the web =]
You're welcome. I am a loyal Firefox user, so I am interested in ANYTHING that can be done to make Firefox even better.