nros rmw-cffi
C vtable for plugging a third-party RMW backend into nros
Loading...
Searching...
No Matches
rmw_service_info_t Struct Reference

#include <rmw_entity.h>

Collaboration diagram for rmw_service_info_t:

Data Fields

rmw_time_point_value_t received_timestamp
rmw_request_id_t request_id
rmw_time_point_value_t source_timestamp

Detailed Description

Per-request metadata — upstream rmw_service_info_t, field for field.

Issue 2081. Filled by take_request_with_info for a request and, since issue 2136, by take_response_with_info for a reply. As in rmw_message_info_t, a field the backend cannot report is ZERO: a timestamp of 0 means "not stamped", and an all-zero request_id.writer_guid means the request id is not reported. The runtime turns each into None, never into a value.

The timestamps are the SENDER's and the RECEIVER's, as upstream's are: for a request, the client's send time and the server's arrival time; for a reply, the server's send time and the client's arrival time.

Field Documentation

◆ received_timestamp

rmw_time_point_value_t rmw_service_info_t::received_timestamp

Receiver's clock when the message was received, ns. 0 = not reported.

◆ request_id

rmw_request_id_t rmw_service_info_t::request_id

The request: who sent it, and its client-assigned sequence number.

◆ source_timestamp

rmw_time_point_value_t rmw_service_info_t::source_timestamp

Sender's clock when the message was sent, ns. 0 = not reported.


The documentation for this struct was generated from the following file: