Lines Matching refs:InterfacePtr

129 using LoggerPtr = mojo::InterfacePtr<Logger>;
138 ### InterfacePtr and InterfaceRequest
142 bindings library: **`InterfacePtr<T>`** and **`InterfaceRequest<T>`**.
145 message pipe endpoints. If an `InterfacePtr<T>` is bound to a message pipe
151 end of an `InterfacePtr<T>`'s pipe -- the receiving end -- until it can be
156 ![Diagram illustrating InterfacePtr and InterfaceRequest on either end of a message pipe](https://d…
191 a bound `InterfacePtr<T>` is bound to a single sequence.
193 An `InterfacePtr<T>` may be unbound by calling its `PassInterface()` method,
194 which returns a new `InterfacePtrInfo<T>`. Conversely, an `InterfacePtr<T>` may
198 The sequence-bound nature of `InterfacePtr<T>` is necessary to support safe
390   `mojo::InterfacePtr<T>` and it is destroyed.
401 `mojo::InterfacePtr<T>`, *etc.*) support setting their connection error handler
440 Once a `mojo::InterfacePtr<T>` is destroyed, it is guaranteed that pending
453 on how the `InterfacePtr<T>` is held:
454 1. The consumer owns the `InterfacePtr<T>`: `set_connection_error_handler`
456 2. The consumer doesn't own the `InterfacePtr<T>`: there are two helpers
464    destructed (e.g. because the owner of the `InterfacePtr<T>` outlives the
470    synchronously while the InterfacePtr<T> is reset or destroyed.
758 using TablePtr = mojo::InterfacePtr<Table>;
768 using DatabasePtr = mojo::InterfacePtr<Database>;
839 Of course we can also send `InterfacePtr`s:
870 common bindings object types: `InterfacePtr`, `InterfaceRequest`, and `Binding`.
956 ### InterfacePtr Sets
959 `InterfacePtr`s for *e.g.* a set of clients observing some event.
1067 Assume you have already got an `InterfacePtr<Foo> foo_ptr`, and you would like
1132 Similarly, assume you have already got an `InterfacePtr<Foo> foo_ptr`, and you
1624 `InterfacePtr` defines the following methods to query or assert remote interface
1633 that this value is cached by the `InterfacePtr` instance to avoid redundant