please if anyone knows how to do this in kmeleon? it makes webpage loading much faster in Mozilla but i cant find this feature in the kmelon options? maybe a line to add to prefs.js file?

thanks in advance

this is from the k-meleon\defaults\pref\all.js file:
----------------------------------------
pref("network.http.pipelining" , false);
pref("network.http.proxy.pipelining", false);

// Always pipeling the very first request: this will only work when you are
// absolutely sure the the site or proxy you are browsing to/through support
// pipelining; the default behavior will be that the browser will first make
// a normal, non-pipelined request, then examine and remember the responce
// and only the subsequent requests to that site will be pipeline
pref("network.http.pipelining.firstrequest", false);

// Max number of requests in the pipeline
pref("network.http.pipelining.maxrequests" , 4);
-------------------------------------------
i've never played with any of it, but you could try adding a few and see what happens...

I don't think pipelining was implemented until sometime after k-m 0.6 was released. Also, pipelining is still supposed to be slightly buggy; supposedly you might get corrupted images.

well, i've enabled these prefs in the beta, where they're listed in the default\prefs\all.js file, and honestly can't tell if they've done anything, since i know nothing about the subject... no corrupted images that i've noticed, though.

I found the relevant mozilla bugs for pipelining:

http://bugzilla.mozilla.org/show_bug.cgi?id=140561
(some pipelined images aren't loading)

http://bugzilla.mozilla.org/show_bug.cgi?id=141179
(Page does not load with pipelining enabled)

The comments for those bugs seem to indicate that IIS/4.0 has problems with pipelining, so the feature has been disabled for those servers only in the trunk build of moz.

I just enabled the prefs in my own build (based on Mozilla 1.1a), and it did in fact turn on pipelining (I ran a sniffer on my server to watch the traffic). I've gotten one broken image so far, but nothing widespread, so it might not be the pipelining's fault. As for how much faster it is? Well, on a cable modem, the majority of the wait for a page is during rendering, not fetching, so I can't really tell. I'll run some more A/B tests to see if I can notice any difference at all.

So I ran some tests. I got all quantitative and sniffed the packets to get precise timings and such. I used this page for testing, as it has many small graphics (suitable for pipelining). And I set "network.http.pipelining.maxrequests" to 8, because I thought that sounded better than 4.

Without pipelining, it takes maybe 8 seconds for just the network activity and uses about 134 packets (both ways). With pipelining, it goes down to 5 seconds and uses around 124 packets.

Conclusion? It *is* faster, but in all honesty, it will have no impact on my life whatsoever. It's like overclocking your processor by 1% -- you feel good about it, but it effectively changes nothing.

It probably has a more noticeable effect on dial-up, though. And at the very least, you can taunt all of your friends about their lame browsers that don't use HTTP pipelining.

...or you can taunt all the network admins about lame servers that don't support it.

my (<28k) dial-up is probably the perfect test case... i'll look into it if they release a beta build where setpref() works... otherwise a/b testing would take a little more effort than i'm willing to expend...

8 -> 5 is like 35-40% gain.

Yea, it doesn't do anything good when viewing single page but should you ask me whether I want to save 3 seconds per each of 200 pages I visit daily then I surely will answer "yes I do"