Closed
Bug 1120652
Opened 10 years ago
Closed 10 years ago
Get rid of FetchDriverObserver::OnResponseEnd()
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
mozilla38
People
(Reporter: nsm, Assigned: tejas.srinivasan95, Mentored)
References
Details
(Whiteboard: [good first bug][lang=C++])
Attachments
(1 file)
2.05 KB,
patch
|
nsm
:
review+
|
Details | Diff | Splinter Review |
Since switching to streams everywhere, an 'end' indication is no longer required. It just complicates our worker release.
Reporter | ||
Updated•10 years ago
|
Blocks: dom-fetch-api
Reporter | ||
Updated•10 years ago
|
Mentor: nsm.nikhil
Whiteboard: [good first bug][lang=C++]
Assignee | ||
Comment 1•10 years ago
|
||
I'd like to work on this bug. I went through the class definition of FetchDriverObserver, but couldn't find a member function OnResponseEnd(). Can you please point me to the relevant code?
Reporter | ||
Comment 2•10 years ago
|
||
(In reply to Tejas Srinivasan from comment #1)
> I'd like to work on this bug. I went through the class definition of
> FetchDriverObserver, but couldn't find a member function OnResponseEnd().
> Can you please point me to the relevant code?
The relevant code will be there once the patches in Bug 1039846 have landed. I will land them today.
Reporter | ||
Comment 3•10 years ago
|
||
The changes have landed. Please go ahead with fixing this. Thanks!
Assignee | ||
Comment 4•10 years ago
|
||
So do I just need to remove the OnResponseEnd() function from the FetchDriverObserver class and its child classes (declaration and definitions)? Is there anything else to do? Do I remove the two function calls as well ([1], [2])?
[1] : https://dxr.mozilla.org/mozilla-central/source/dom/fetch/FetchDriver.cpp#475
[2] : https://dxr.mozilla.org/mozilla-central/source/dom/fetch/FetchDriver.cpp#486
Sorry for the noob doubts, I'm kinda new around here.
Reporter | ||
Comment 5•10 years ago
|
||
So after some thinking, we can't really get rid of OnResponseEnd() entirely. On workers, we add a feature to keep the worker alive until the fetch is done. If we remove the feature in OnResponseAvailable() we will end up allowing the worker to terminate before the response is complete. So, let's get rid of MainThreadFetchResolver::OnResponseEnd(), and provide a default empty definition of it in FetchDriverObserver.
Assignee | ||
Comment 6•10 years ago
|
||
(In reply to Nikhil Marathe [:nsm] (needinfo? please) from comment #5)
> So, let's get rid of MainThreadFetchResolver::OnResponseEnd(), and provide a default
> empty definition of it in FetchDriverObserver.
OK, but what about the two function calls? Will any modification be required on that end?
Reporter | ||
Comment 7•10 years ago
|
||
No changes.
Assignee | ||
Comment 8•10 years ago
|
||
Kindly review the patch I have attached. Thanks.
Attachment #8549429 -
Flags: review?(nsm.nikhil)
Reporter | ||
Updated•10 years ago
|
Attachment #8549429 -
Flags: review?(nsm.nikhil) → review+
Assignee | ||
Updated•10 years ago
|
Keywords: checkin-needed
Comment 9•10 years ago
|
||
Assignee: nobody → tejas.srinivasan95
Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla38
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•