Commit 253a2b38 authored by Ken MacKay's avatar Ken MacKay Committed by Commit Bot

[Chromecast] Use PendingReceiver for external Mojo BindInterface

To match the semantics of the new PendingReceiver / Remote APIs.

Merge-With: eureka-internal/342617
Change-Id: I1cfed9313351dff96307b1e63bb2ed4d1e1053b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1959927Reviewed-by: default avatarYuchen Liu <yucliu@chromium.org>
Commit-Queue: Kenneth MacKay <kmackay@chromium.org>
Cr-Commit-Position: refs/heads/master@{#723471}
parent 8cec29f7
......@@ -57,16 +57,8 @@ class ExternalConnector {
// will remain in progress until the service is registered.
template <typename Interface>
void BindInterface(const std::string& service_name,
mojo::InterfacePtr<Interface>* ptr) {
BindInterface(service_name, Interface::Name_,
mojo::MakeRequest(ptr).PassMessagePipe());
}
template <typename Interface>
void BindInterface(const std::string& service_name,
mojo::PendingRemote<Interface>* ptr) {
BindInterface(service_name, Interface::Name_,
ptr->InitWithNewPipeAndPassReceiver().PassPipe());
mojo::PendingReceiver<Interface> receiver) {
BindInterface(service_name, Interface::Name_, receiver.PassPipe());
}
virtual void BindInterface(const std::string& service_name,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment