This is an RFE to add support for pipelining in 5.0.
setting paulmac as QA contact for all gagan's bugs (sorry for the spam)
Component: NetLib → Networking Library
Product: MozillaClassic → Browser
necko? -> m8
While pipelining is important, it certainly isn't mission critical right now.
Changing all Networking Library/Browser bugs to Networking-Core component for Browser. Occasionally, Bugzilla will burp and cause Verified bugs to reopen when I do this in a bulk change. If this happens, I will fix. ;-)
Bulk move of all Networking-Core (to be deleted component) bugs to new Networking component.
pipelining is a critical feature needed for satellite-based networks. It is the most important enhancement that could be made for a "satellite-friendly" browser.
Severity: enhancement → critical
Assignee: gagan → ruslan
Status: ASSIGNED → NEW
Pipelining is landed.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
I was supprised to see this bug marked fixed ,when CVS says "pipelining not on by default"?
You can enable it by saying pref ("network.http.pipelining", true). Let us play with it for a little bit. It's good enough for testing purposes. Especially when there are still some servers in the world which claim http/1.1, but in reality screw things up.
verified: WinNT 2000070508
Status: RESOLVED → VERIFIED
Component: Networking → Networking: HTTP
Summary: Add support for pipelining → Add support for pipelining ("network.http.pipelining")
You need to log in before you can comment on or make changes to this bug.