Lines Matching refs:InterfaceRequest

130 using LoggerRequest = mojo::InterfaceRequest<Logger>;
138 ### InterfacePtr and InterfaceRequest
142 bindings library: **`InterfacePtr<T>`** and **`InterfaceRequest<T>`**.
150 An `InterfaceRequest<T>` is essentially just a typed container to hold the other
152 routed to some implementation which will **bind** it. The `InterfaceRequest<T>`
156 ![Diagram illustrating InterfacePtr and InterfaceRequest on either end of a message pipe](https://d…
188 similar to an `InterfaceRequest<T>` in that it merely holds onto a pipe handle
190 `InterfaceRequest<T>` are safe to move freely from sequence to sequence, whereas
216 But as mentioned above, `InterfaceRequest` *doesn't actually do anything*, so
226 with a single bound message pipe endpoint (via a `mojo::InterfaceRequest<T>`),
244   // instance per client is to take an InterfaceRequest in the constructor.
336   // instance per client is to take an InterfaceRequest in the constructor.
744 precisely to the `InterfaceRequest<T>` type discussed in the sections above, and
759 using TableRequest = mojo::InterfaceRequest<Table>;
769 using DatabaseRequest = mojo::InterfaceRequest<Database>;
816 `mojo::InterfaceRequest<db::mojom::Table>`, which we know is just a
870 common bindings object types: `InterfacePtr`, `InterfaceRequest`, and `Binding`.