template <typename BuilderImpl>class WireTableBaseBuilder
Defined at line 2172 of file fidling/gen/sdk/fidl/fuchsia.diagnostics/fuchsia.diagnostics/cpp/fidl/fuchsia.diagnostics/cpp/wire_types.h
Public Methods
::fuchsia_diagnostics::wire::SampleDatum Build ()Build and return the table. The builder should not be used after this.
bool has_selector ()void clear_selector ()Clears the selector field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
::fuchsia_diagnostics::wire::SelectorArgument & selector ()The selector to check.
BuilderImpl & selector (Wrapper_Ignore_Me_< ::fidl::ObjectView< ::fuchsia_diagnostics::wire::SelectorArgument>> elem)The selector to check.
bool has_strategy ()void clear_strategy ()Clears the strategy field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
::fuchsia_diagnostics::wire::SampleStrategy & strategy ()The strategy by which the server decides to notify the client.
BuilderImpl & strategy (::fuchsia_diagnostics::wire::SampleStrategy elem)The strategy by which the server decides to notify the client.
bool has_interval_secs ()void clear_interval_secs ()Clears the interval_secs field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
int64_t & interval_secs ()The interval at which this datum should be sampled.
Each `SampleDatum` has its own specified interval. It is preferred to send
as many selectors on one `Sample` connection as possible, to allow
Archivist to batch requests. However, Archivist will query at a period that
is the greatest common divisor of all intervals. So, balance the desire for
a small number of `Sample` connections with keeping the intervals compatible.
Example: two data with intervals of 3 and 4 respectively would check for work
every second. Archivist won't actually sample if neither batch is ready, but
it will check.
Example: two data with intervals of 10 and 5 respectively would only check for
work every 5 seconds.
(In practice, the calculated sample period must be valid. See
MINIMUM_SAMPLE_PERIOD_SECONDS above.)
BuilderImpl & interval_secs (Wrapper_Ignore_Me_< ::fidl::ObjectView<int64_t>> elem)The interval at which this datum should be sampled.
Each `SampleDatum` has its own specified interval. It is preferred to send
as many selectors on one `Sample` connection as possible, to allow
Archivist to batch requests. However, Archivist will query at a period that
is the greatest common divisor of all intervals. So, balance the desire for
a small number of `Sample` connections with keeping the intervals compatible.
Example: two data with intervals of 3 and 4 respectively would check for work
every second. Archivist won't actually sample if neither batch is ready, but
it will check.
Example: two data with intervals of 10 and 5 respectively would only check for
work every 5 seconds.
(In practice, the calculated sample period must be valid. See
MINIMUM_SAMPLE_PERIOD_SECONDS above.)
Protected Methods
void WireTableBaseBuilder< ::fuchsia_diagnostics::wire::SampleDatum, BuilderImpl> (::fidl::ObjectView< ::fidl::WireTableFrame< ::fuchsia_diagnostics::wire::SampleDatum>> && frame)