template <typename BuilderImpl>class WireTableBaseBuilder
Defined at line 1120 of file fidling/gen/sdk/fidl/fuchsia.component.runner/fuchsia.component.runner/cpp/fidl/fuchsia.component.runner/cpp/wire_types.h
Public Methods
::fuchsia_component_runner::wire::ComponentControllerOnEscrowRequest Build ()Build and return the table. The builder should not be used after this.
bool has_outgoing_dir ()void clear_outgoing_dir ()Clears the outgoing_dir field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
::fidl::ServerEnd< ::fuchsia_io::Directory> & outgoing_dir ()Escrow the outgoing directory server endpoint. Whenever the
component is started, the framework will return this channel via
[`ComponentStartInfo.outgoing_dir`].
BuilderImpl & outgoing_dir (::fidl::ServerEnd< ::fuchsia_io::Directory> elem)Escrow the outgoing directory server endpoint. Whenever the
component is started, the framework will return this channel via
[`ComponentStartInfo.outgoing_dir`].
bool has_escrowed_dictionary ()void clear_escrowed_dictionary ()Clears the escrowed_dictionary field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
::fuchsia_component_sandbox::wire::DictionaryRef & escrowed_dictionary ()Escrow some user defined state. Whenever the component is started,
the framework will return these handles via
[`ComponentStartInfo.escrowed_dictionary`].
The framework will not wait for any signals on these objects.
## Example
Let's say a component needs to escrow an event pair that represents
the result of some expensive calculation. It can create a
dictionary, put the event pair inside with an appropriate key
(e.g. `"my_event_pair"`), then check for that entry on startup.
Note that this is deprecated, please use
`escrowed_dictionary_handle` instead.
BuilderImpl & escrowed_dictionary (::fuchsia_component_sandbox::wire::DictionaryRef elem)Escrow some user defined state. Whenever the component is started,
the framework will return these handles via
[`ComponentStartInfo.escrowed_dictionary`].
The framework will not wait for any signals on these objects.
## Example
Let's say a component needs to escrow an event pair that represents
the result of some expensive calculation. It can create a
dictionary, put the event pair inside with an appropriate key
(e.g. `"my_event_pair"`), then check for that entry on startup.
Note that this is deprecated, please use
`escrowed_dictionary_handle` instead.
bool has_escrowed_dictionary_handle ()void clear_escrowed_dictionary_handle ()Clears the escrowed_dictionary_handle field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
::zx::eventpair & escrowed_dictionary_handle ()Escrow some user defined state. Whenever the component is started,
the framework will return these handles via
[`ComponentStartInfo.escrowed_dictionary`].
The framework will not wait for any signals on these objects.
## Example
Let's say a component needs to escrow an event pair that represents
the result of some expensive calculation. It can create a
dictionary, put the event pair inside with an appropriate key
(e.g. `"my_event_pair"`), then check for that entry on startup.
BuilderImpl & escrowed_dictionary_handle (::zx::eventpair elem)Escrow some user defined state. Whenever the component is started,
the framework will return these handles via
[`ComponentStartInfo.escrowed_dictionary`].
The framework will not wait for any signals on these objects.
## Example
Let's say a component needs to escrow an event pair that represents
the result of some expensive calculation. It can create a
dictionary, put the event pair inside with an appropriate key
(e.g. `"my_event_pair"`), then check for that entry on startup.
Protected Methods
void WireTableBaseBuilder< ::fuchsia_component_runner::wire::ComponentControllerOnEscrowRequest, BuilderImpl> (::fidl::ObjectView< ::fidl::WireTableFrame< ::fuchsia_component_runner::wire::ComponentControllerOnEscrowRequest>> && frame)