4 ms·

What is the good reason?

• patio11 18y ago
  See: http://www.mozilla.org/projects/netlib/http/pipelining-faq.html http://www.mozilla.org/projects/netlib/http/pipelining-faq.h... This obviously has the potential to introduce a new category of evangelism bugs, since no other popular web browsers implement pipelining. http://hubpages.com/hub/Firefox-pipelining-speed-tweak-may-actually-slow-down-your-browser http://hubpages.com/hub/Firefox-pipelining-speed-tweak-may-a... URL says it all.
  • trapper 18y ago
    The second article notes that for most modern webservers for those not using a modem (really, they still have those?) it should be faster. And this: "Firefox will only send a maximum of 8 HTTP requests at a time in any case" - really? Anyone know if there is a good reason?
    • eli 18y ago
      Because most people don't want each client making >8 connections to their web server at once. Nor would making more connections necessarily be faster.
    • bmj 18y ago
      The second article notes that for most modern webservers for those not using a modem (really, they still have those?) it should be faster. Oh, yes indeed-y. I'm writing modem control code for a compact framework app right now.