Example: How users configure channels for online/standby redundancy. More...

#include <stdint.h>
#include <stdbool.h>
#include <string.h>
#include <stdio.h>
#include "rte/channel_link/rte_channel.h"
#include "rte/voter/rte_voter.h"
#include "rte/status/rte_status.h"

Include dependency graph for channel_configuration_example.c:

Data Structures
struct	tcp_channel_config_t
struct	udp_channel_config_t
struct	shm_channel_config_t
struct	fifo_channel_config_t
struct	channel_wrapper_t

Enumerations
enum	channel_type_t { CHANNEL_TYPE_TCP , CHANNEL_TYPE_UDP , CHANNEL_TYPE_SHM , CHANNEL_TYPE_FIFO }

Functions
static rte_status_t	app_backend_send (void channel, const void data, size_t size)
	Dispatcher send callback Routes to appropriate transport based on channel type.
static rte_status_t	app_backend_recv (void channel, void data, size_t size, uint32_t timeout_ms)
	Dispatcher receive callback Routes to appropriate transport based on channel type.
void	example_tcp_based_redundancy (void)
void	example_local_redundancy (void)
void	example_hybrid_configuration (void)
int	main (void)

Detailed Description

Example: How users configure channels for online/standby redundancy.

This example shows:

Creating different channel types with user-specified parameters
TCP/IP for remote standby communication (primary use case)
Optional fallback channels (UDP, shared memory for local)
Wrapping in rte_voter for voting/redundancy (ADR-025)
Dispatcher pattern for mixed transport types

User responsibility: Provide configuration values (IPs, ports, paths) Framework responsibility: Voting, health tracking, safe-state OS integrator responsibility: Actual send/recv implementations

Definition in file channel_configuration_example.c.