Per-client state structure for server-side client management. More...

#include <lib/network/client.h>

Data Fields
socket_t	socket

acip_transport_t *	transport

asciichat_thread_t	receive_thread

atomic_uint	client_id

char	display_name [MAX_DISPLAY_NAME_LEN]

char	client_ip [INET_ADDRSTRLEN]

int	port

bool	can_send_video

bool	can_send_audio

bool	wants_stretch

atomic_bool	is_sending_video

atomic_bool	is_sending_audio

void *	opus_decoder

terminal_capabilities_t	terminal_caps

bool	has_terminal_caps

char	client_palette_chars [256]

size_t	client_palette_len

char	client_luminance_palette [256]

palette_type_t	client_palette_type

bool	client_palette_initialized

atomic_ushort	width

atomic_ushort	height

atomic_bool	active

atomic_bool	shutting_down

atomic_bool	protocol_disconnect_requested

time_t	connected_at

uint64_t	frames_sent

uint64_t	frames_received

uint32_t	frames_received_logged

video_frame_buffer_t *	incoming_video_buffer

audio_ring_buffer_t *	incoming_audio_buffer

video_frame_buffer_t *	outgoing_video_buffer

packet_queue_t *	audio_queue

asciichat_thread_t	send_thread

atomic_bool	send_thread_running

atomic_int	last_rendered_grid_sources

atomic_int	last_sent_grid_sources

void *	send_buffer

size_t	send_buffer_size

void *	crypto_plaintext_buffer

size_t	crypto_plaintext_size

void *	crypto_ciphertext_buffer

size_t	crypto_ciphertext_size

asciichat_thread_t	video_render_thread

asciichat_thread_t	audio_render_thread

atomic_bool	video_render_thread_running

atomic_bool	audio_render_thread_running

struct timespec	last_video_render_time

struct timespec	last_audio_render_time

mutex_t	client_state_mutex

mutex_t	send_mutex

crypto_handshake_context_t	crypto_handshake_ctx

bool	crypto_initialized

packet_type_t	pending_packet_type

void *	pending_packet_payload

size_t	pending_packet_length

UT_hash_handle	hh

Detailed Description

Per-client state structure for server-side client management.

Represents complete state for a single connected client in the ascii-chat server. This structure stores all client-specific information including network connection, media capabilities, terminal settings, threading state, and synchronization primitives.

CORE FIELDS:

Network: Socket, IP address, port, thread handles
Media: Video/audio capabilities, stream state, buffers
Terminal: Capabilities, palette cache, dimensions
Threading: Send/receive/render thread handles and flags
Synchronization: Mutexes for thread-safe state access
Crypto: Cryptographic handshake context for secure communication

THREADING MODEL:

Each client has dedicated threads:

receive_thread: Handles incoming packets (protocol processing)
send_thread: Manages outgoing packet delivery (packet queues)
video_render_thread: Generates ASCII frames at 60fps
audio_render_thread: Mixes audio streams at 172fps

BUFFER MANAGEMENT:

incoming_video_buffer: Double-buffered video frames from client
incoming_audio_buffer: Ring buffer for client's audio samples
outgoing_video_buffer: Double-buffered ASCII frames to send
audio_queue: Packet queue for audio packets to send

MEMORY MANAGEMENT:

Pre-allocated buffers to avoid malloc/free in hot paths
send_buffer: For packet assembly
crypto_plaintext_buffer: For encryption plaintext
crypto_ciphertext_buffer: For encryption ciphertext

Note: All atomic fields are thread-safe for concurrent access.; Buffer pointers are set once during client creation and never change.; Thread handles are valid only when threads are running.

Definition at line 77 of file lib/network/client.h.