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

#include <rmw_entity.h>

Data Fields

uint8_t _reserved [8]
 
void * backend_data
 
const char * service_name
 
const char * type_name
 

Detailed Description

Service-server entity.

Service entities have no QoS in the nros subset (the upstream rmw_qos_profile_services_default distinction does not generalise across non-DDS backends — see book concepts/ros2-comparison.md).

No can_loan_messages field — service request/reply currently always goes through try_recv_request / send_reply byte-buffer APIs. If a future backend wants service-side lending, the _reserved[8] block accommodates the bool + 7 padding bytes without an ABI break.

Field Documentation

◆ _reserved

uint8_t nros_rmw_service_server_t::_reserved[8]

Reserved for future fields; must be zero.

◆ backend_data

void* nros_rmw_service_server_t::backend_data

Opaque backend state. NULL if creation failed.

◆ service_name

const char* nros_rmw_service_server_t::service_name

Service name (borrowed; outlives the server).

◆ type_name

const char* nros_rmw_service_server_t::type_name

Fully-qualified service type name (e.g., "example_interfaces/srv/AddTwoInts"). Borrowed.


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