Closed
Bug 481612
Opened 15 years ago
Closed 15 years ago
Should send activity distributor notifications also for STATUS_RECEIVING_FROM
Categories
(Core :: Networking: HTTP, defect)
Core
Networking: HTTP
Tracking
()
RESOLVED
FIXED
mozilla1.9.1
People
(Reporter: Biesinger, Assigned: Biesinger)
Details
(Keywords: fixed1.9.1)
Attachments
(1 file)
1.85 KB,
patch
|
Biesinger
:
review+
Biesinger
:
superreview+
beltzner
:
approval1.9.1+
|
Details | Diff | Splinter Review |
http://mxr.mozilla.org/mozilla-central/source/netwerk/protocol/http/src/nsHttpTransaction.cpp#355 355 // nsHttpChannel synthesizes progress events in OnDataAvailable 356 if (status == nsISocketTransport::STATUS_RECEIVING_FROM) 357 return; 358 359 if (mActivityDistributor) { 360 // upon STATUS_WAITING_FOR; report request body sent 361 if ((mHasRequestBody) && 362 (status == nsISocketTransport::STATUS_WAITING_FOR)) 363 mActivityDistributor->ObserveActivity( 364 mChannel, 365 NS_HTTP_ACTIVITY_TYPE_HTTP_TRANSACTION, 366 NS_HTTP_ACTIVITY_SUBTYPE_REQUEST_BODY_SENT, 367 LL_ZERO, LL_ZERO, EmptyCString()); 368 369 // report the status and progress 370 mActivityDistributor->ObserveActivity( 371 mChannel, 372 NS_HTTP_ACTIVITY_TYPE_SOCKET_TRANSPORT, 373 static_cast<PRUint32>(status), 374 LL_ZERO, 375 progress, 376 EmptyCString()); 377 } So this code doesn't call ObserveActivity for receiving_from, and nsHttpChannel doesn't do it either when synthesizing the status messages. So, this code should do the receiving_from check after sending the notification.
Assignee | ||
Updated•15 years ago
|
Assignee: bienvenu → cbiesinger
Assignee | ||
Comment 1•15 years ago
|
||
report+patch was by Bryan McQuade, r+sr=me
Attachment #365634 -
Flags: superreview+
Attachment #365634 -
Flags: review+
Assignee | ||
Comment 2•15 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/b145e6658509
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•15 years ago
|
Attachment #365634 -
Flags: approval1.9.1?
Assignee | ||
Comment 3•15 years ago
|
||
Comment on attachment 365634 [details] [diff] [review] patch I'd like to get this into ff 3.1 as well, it is a pretty safe patch (no change in behaviour unless you install an extension that makes use of this); it just moves around a bit of code. it allows extensions to keep track of the exact timing of receiving data, so that they can tell web developers more details about the performance of their web pages.
Assignee | ||
Comment 4•15 years ago
|
||
Note that Firebug and Livehttpheaders do not use this interface and thus can't be adversely affected by this change.
Comment 5•15 years ago
|
||
Comment on attachment 365634 [details] [diff] [review] patch a191=beltzner; biesi did a search and discovered no add-ons that use this method, so looks ok, compat-wise. biesi: it'd be grand if you could add tests for this and/or ensure that it's a documented method on MDC.
Attachment #365634 -
Flags: approval1.9.1? → approval1.9.1+
Assignee | ||
Comment 6•15 years ago
|
||
Pushed to 1.9.1 http://hg.mozilla.org/releases/mozilla-1.9.1/rev/c6d941dfc5a3 Writing a test is difficult; doing this in JS asserts in some bad ways, making the test fail.
Keywords: fixed1.9.1
Assignee | ||
Updated•15 years ago
|
Target Milestone: --- → mozilla1.9.1
Comment 7•15 years ago
|
||
If that's true, how can this be verified? Curious is all :)
You need to log in
before you can comment on or make changes to this bug.
Description
•