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

#include <rmw_entity.h>

Collaboration diagram for rmw_topic_endpoint_info_t:
Collaboration graph
[legend]

Data Fields

rmw_gid_t endpoint_gid
 
rmw_endpoint_type_t endpoint_type
 
const char * node_name
 
const char * node_namespace
 
rmw_qos_profile_t qos_profile
 
const char * topic_type
 

Detailed Description

One discovered endpoint — upstream rmw_topic_endpoint_info_t.

Every string is BORROWED for the duration of the visit that hands this out; a caller that needs one past the callback copies it. That is what lets the graph slots stream without an allocator.

Field Documentation

◆ endpoint_gid

rmw_gid_t rmw_topic_endpoint_info_t::endpoint_gid

The endpoint's identity; data all-zero when the backend has none.

◆ endpoint_type

rmw_endpoint_type_t rmw_topic_endpoint_info_t::endpoint_type

Publisher or subscription.

◆ node_name

const char* rmw_topic_endpoint_info_t::node_name

Node that owns the endpoint.

◆ node_namespace

const char* rmw_topic_endpoint_info_t::node_namespace

That node's namespace.

◆ qos_profile

rmw_qos_profile_t rmw_topic_endpoint_info_t::qos_profile

The GRANTED profile, not the requested one — which is the whole reason a consumer asks. A backend that cannot read back a remote's granted QoS reports what it MATCHED on, and must not substitute the local entity's requested profile.

◆ topic_type

const char* rmw_topic_endpoint_info_t::topic_type

Fully-qualified type on the wire, e.g. "std_msgs/msg/Int32".


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