3 ms·
If aggressive pipelining worked well enough then Mozilla would turn it on by default. The fact they don't is more than enough reason for Google to not test agai
by ZeroGravitas 12y ago
If aggressive pipelining worked well enough then Mozilla would turn it on by default. The fact they don't is more than enough reason for Google to not test against it.
- bsdetector 12y agoMozilla and Google claim there are bad servers out there that pipelining doesn't work with, but yet neither were able to identify those bad servers or reproduce the problems -- probably because the bad software is Superfish and other malware. You don't see problems with iOS Safari using pipelining. Maybe they should have asked Kaspersky. If you have a clean system pipelining works great.
- ZeroGravitas 12y agoFor anyone interested, a summary from the decision maker at Mozilla who made this call: https://bugzilla.mozilla.org/show_bug.cgi?id=264354#c65 https://bugzilla.mozilla.org/show_bug.cgi?id=264354#c65 "It pains me as I believe firefox has the most sophisticated pipelining algorithm ever built, but the fundamental approach is simply flawed in ways that multiplexing is not. Let's put energy into making multiplexing a success."
- bsdetector 12y ago> "Let's put energy into making multiplexing a success." In other words, the guy just doesn't want to work on pipelining anymore, not that it doesn't work well. He also said "it's good" and kept it enabled for mobile because "the higher rtts tip the balance in its favor" -- and you're telling somebody with satellite internet not to use it to reduce page load time for the vast majority pages out there that are not SSL (and so not HTTP2) or are on old servers. Really?
- iotku 12y agoSeems to work pretty well for me, now only if I used non SSL sites more often. Go figure I find a solution to most of my issues I have with Sat around the time I'm moving somewhere with hopefully better internet soon.