class LifecycleOnEscrowRequest

Defined at line 31 of file fidling/gen/sdk/fidl/fuchsia.process.lifecycle/fuchsia.process.lifecycle/cpp/fidl/fuchsia.process.lifecycle/cpp/natural_types.h

Public Methods

void LifecycleOnEscrowRequest (Storage_ storage)

bool IsEmpty ()

void LifecycleOnEscrowRequest ()

Defined at line 37 of file fidling/gen/sdk/fidl/fuchsia.process.lifecycle/fuchsia.process.lifecycle/cpp/fidl/fuchsia.process.lifecycle/cpp/natural_types.h

void LifecycleOnEscrowRequest (LifecycleOnEscrowRequest && )

Defined at line 38 of file fidling/gen/sdk/fidl/fuchsia.process.lifecycle/fuchsia.process.lifecycle/cpp/fidl/fuchsia.process.lifecycle/cpp/natural_types.h

LifecycleOnEscrowRequest & operator= (LifecycleOnEscrowRequest && )

Defined at line 39 of file fidling/gen/sdk/fidl/fuchsia.process.lifecycle/fuchsia.process.lifecycle/cpp/fidl/fuchsia.process.lifecycle/cpp/natural_types.h

const std::optional< ::fidl::ServerEnd< ::fuchsia_io::Directory>> & outgoing_dir ()

Escrow the outgoing directory server endpoint. Whenever the

component is started again, this will be returned as the

`PA_DIRECTORY_REQUEST` processargs entry.

::std::optional< ::fidl::ServerEnd< ::fuchsia_io::Directory>> & outgoing_dir ()

Escrow the outgoing directory server endpoint. Whenever the

component is started again, this will be returned as the

`PA_DIRECTORY_REQUEST` processargs entry.

LifecycleOnEscrowRequest & outgoing_dir (std::optional< ::fidl::ServerEnd< ::fuchsia_io::Directory>> value)

Escrow the outgoing directory server endpoint. Whenever the

component is started again, this will be returned as the

`PA_DIRECTORY_REQUEST` processargs entry.

const std::optional< ::fuchsia_component_sandbox::DictionaryRef> & escrowed_dictionary ()

Escrow some user defined state. Whenever the component is started

again, this will be returned as the `PA_ESCROWED_DICTIONARY`

processargs entry.

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.

::std::optional< ::fuchsia_component_sandbox::DictionaryRef> & escrowed_dictionary ()

Escrow some user defined state. Whenever the component is started

again, this will be returned as the `PA_ESCROWED_DICTIONARY`

processargs entry.

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.

LifecycleOnEscrowRequest & escrowed_dictionary (std::optional< ::fuchsia_component_sandbox::DictionaryRef> value)

Escrow some user defined state. Whenever the component is started

again, this will be returned as the `PA_ESCROWED_DICTIONARY`

processargs entry.

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.

const std::optional< ::zx::eventpair> & escrowed_dictionary_handle ()

Escrow some user defined state. Whenever the component is started

again, this will be returned as the `PA_ESCROWED_DICTIONARY`

processargs entry.

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.

::std::optional< ::zx::eventpair> & escrowed_dictionary_handle ()

Escrow some user defined state. Whenever the component is started

again, this will be returned as the `PA_ESCROWED_DICTIONARY`

processargs entry.

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.

LifecycleOnEscrowRequest & escrowed_dictionary_handle (std::optional< ::zx::eventpair> value)

Escrow some user defined state. Whenever the component is started

again, this will be returned as the `PA_ESCROWED_DICTIONARY`

processargs entry.

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.

void LifecycleOnEscrowRequest (::fidl::internal::DefaultConstructPossiblyInvalidObjectTag )

Friends

class MemberVisitor

class NaturalTableCodingTraits