template <>class WireSyncClientImpl
Defined at line 894 of file fidling/gen/sdk/fidl/fuchsia.cobalt/fuchsia.cobalt/cpp/fidl/fuchsia.cobalt/cpp/wire_messaging.h
Methods to make a sync FIDL call directly on an unowned handle or a
const reference to a |::fidl::ClientEnd
<
::fuchsia_cobalt::Controller>|,
avoiding setting up a client.
Public Methods
::fidl::WireResult< ::fuchsia_cobalt::Controller::RequestSendSoon> RequestSendSoon ()Requests that the collection of Observations that are currently cached
locally be sent to the Cobalt server soon. Cobalt will send the
Observations in one or more batches and will retry several times upon
failure. The response occurs only after that procedure is completed. A
return value of true indicates that all Observations were successfully
sent. A return value of false indicates otherwise.
Allocates 40 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::WireResult< ::fuchsia_cobalt::Controller::GenerateAggregatedObservations> GenerateAggregatedObservations (uint32_t day_index, ::fidl::VectorView< ::fuchsia_cobalt::wire::ReportSpec> report_specs)Triggers Cobalt to generate Observations based on locally aggregated
event data and write them to the local ObservationStore. In a non-test
environment this would normally be done periodically by a background
thread. In a test environment this method should be invoked against an
instance of the Cobalt FIDL service that was passed the flag
--start_event_aggregator_worker=false.
`day_index` The index of the day for which locally aggregated
Observations should be generated.
`report_specs` A vector of specifications identifying the reports to
return the number of observations for.
Returns a vector whose k-th element is the number of observations
generated for the k-th element of `report_specs`. If `report_specs`
is the empty vector, then an empty vector is returned.
Request is heap-allocated. Response is heap-allocated.
::fidl::WireResult< ::fuchsia_cobalt::Controller::ListenForInitialized> ListenForInitialized ()Requests that the caller be notified after the Cobalt FIDL service
is in the fully-initialized state.
Cobalt starts serving requests before it is fully initialized. In this
pre-initialized state it will buffer incoming log events in memory
but not complete their processing. After Cobalt becomes fully
initialized the events in the bufer are fully processed.
A partial list of things that must happen before Cobalt enters the
fully-initialized state are:
- Cobalt must by notified by the timekeeper service that the system
clock has become accurate--usually because the time has been
fetched from a trusted network resource.
The callback to this method will be invoked after Cobalt transistions
Allocates 32 bytes of message buffer on the stack. No heap allocation necessary.