Closed
Bug 1739001
Opened 3 years ago
Closed 3 years ago
Make it possible to generate connection info for TRRServiceChannel asynchronously
Categories
(Core :: Networking: DNS, task, P2)
Core
Networking: DNS
Tracking
()
RESOLVED
FIXED
96 Branch
Tracking | Status | |
---|---|---|
firefox96 | --- | fixed |
People
(Reporter: kershaw, Assigned: kershaw)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [necko-triaged])
Attachments
(2 files)
Currently, when a TRRServiceChannel
wants to do proxy resolution, it's done by posting a runnable to main thread and wait for the result dispatched back to background thread. When socket process is enabled, this becomes worse, since proxy resolution is done in parent process.
To improve this, I think we can pre-fetch
the connection info for TRRServiceChannel
and let it use the pre-generated connection info to connect. To make sure the pre-generated connection info is up-to-date, we should update it when detecting any proxy change.
Assignee | ||
Comment 1•3 years ago
|
||
Assignee | ||
Comment 2•3 years ago
|
||
Depends on D130814
Pushed by kjang@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ef33201f2f57
Pre-fetch connection info for TRRServiceChannel, r=necko-reviewers,valentin,nhnt11
https://hg.mozilla.org/integration/autoland/rev/1796ac6abb07
Test case, r=necko-reviewers,valentin
Comment 4•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/ef33201f2f57
https://hg.mozilla.org/mozilla-central/rev/1796ac6abb07
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox96:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 96 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•