Add mojo version for new HostResolver API.
Implemented as a single ResolveHost method in NetworkContext for now with all the real work in a separate ResolveHostRequest class that we'll be able to use from multiple places if we copy or move the ResolveHost method to other interfaces. Per recent discussions, we've diverged from the design in the doc. Responses are now always sent via a dedicated response client mojo pipe instead of using response callbacks on the request pipe. This makes cancellation and callback control much clearer and bug-proofed for clients because it's always clear which pipe controls the callbacks and the callbacks are usually tightly bound to the relevant mojo binding. The design doc will be updated after this CL is landed. Design doc: https://docs.google.com/document/d/1NmADJX00oRe9TxFCJTWl8ofdfyR22pbKT8-5Ad5lBsU Bug: 821021 Cq-Include-Trybots: luci.chromium.try:linux_mojo Change-Id: Ib0ae407008fdbec089437083796cae725cd8d8d0 Reviewed-on: https://chromium-review.googlesource.com/1113665Reviewed-by:Tom Sepez <tsepez@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Commit-Queue: Eric Orth <ericorth@chromium.org> Cr-Commit-Position: refs/heads/master@{#580325}
Showing
This diff is collapsed.
Please register or sign in to comment