Closed
Bug 99562
Opened 23 years ago
Closed 23 years ago
nsHttpTransaction should own the nsIProgressEventSink proxy instead of nsHttpConnection
Categories
(Core :: Networking: HTTP, defect, P3)
Core
Networking: HTTP
Tracking
()
VERIFIED
FIXED
mozilla0.9.5
People
(Reporter: darin.moz, Assigned: darin.moz)
References
Details
(Whiteboard: fixed-on-trunk)
Attachments
(1 file)
|
8.44 KB,
patch
|
gagan
:
review+
mscott
:
superreview+
|
Details | Diff | Splinter Review |
nsIProgressEventSink should be implemented by nsHttpTransaction instead of
nsHttpConnection. this is necessary to support pipelining, in which requests
from different threads could be satisfied by the same connection.
|
Assignee | |
Updated•23 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla0.9.5
|
|
Assignee | |
Comment 1•23 years ago
|
||
|
|
Assignee | |
Comment 2•23 years ago
|
||
revised summary
Summary: nsIProgressEventSink should be implemented by nsHttpTransaction instead of nsHttpConnection → nsHttpTransaction should own the nsIProgressEventSink proxy instead of nsHttpConnection
Comment on attachment 49300 [details] [diff] [review]
v1.0 makes nsHttpConnection not own the nsIProgressEventSink proxy
r=gagan
Attachment #49300 -
Flags: review+
|
||
Comment 4•23 years ago
|
||
Comment on attachment 49300 [details] [diff] [review]
v1.0 makes nsHttpConnection not own the nsIProgressEventSink proxy
sr=mscott
Attachment #49300 -
Flags: superreview+
|
|
Assignee | |
Updated•23 years ago
|
Whiteboard: ready-to-land
|
|
Assignee | |
Comment 5•23 years ago
|
||
fixed-on-trunk
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Whiteboard: ready-to-land → fixed-on-trunk
gagan: can you mark this bug verified if you are satisfied the code change is in?
You need to log in
before you can comment on or make changes to this bug.
Description
•