Closed
Bug 2487
Opened 26 years ago
Closed 25 years ago
Add support for pipelining ("network.http.pipelining")
Categories
(Core :: Networking: HTTP, defect, P2)
Tracking
()
VERIFIED
FIXED
M15
People
(Reporter: paulmac, Assigned: ruslan)
References
Details
This is an RFE to add support for pipelining in 5.0.
Reporter | ||
Comment 1•26 years ago
|
||
setting paulmac as QA contact for all gagan's bugs (sorry for the spam)
Reporter | ||
Updated•26 years ago
|
Component: NetLib → Networking Library
Product: MozillaClassic → Browser
Updated•26 years ago
|
Target Milestone: M7
Updated•26 years ago
|
Target Milestone: M7 → M8
Comment 2•26 years ago
|
||
necko? -> m8
Updated•26 years ago
|
Target Milestone: M8 → M10
Comment 3•26 years ago
|
||
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
Pipelining is landed.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 9•25 years ago
|
||
I was supprised to see this bug marked fixed ,when CVS says "pipelining not on
by default"?
Assignee | ||
Comment 10•25 years ago
|
||
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.
Reporter | ||
Updated•25 years ago
|
QA Contact: paulmac → tever
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.
Description
•