How theldus/wsserver works
Main Components
a) Core WebSocket Server Components:
• Connection Handler (manages client connections)
• Event System (handles onopen, onclose, onmessage events)
• Thread Manager (for per-client thread handling)
• Frame Handler (for WebSocket frame processing)
b) Protocol Components:
• Handshake Manager (opening/closing handshakes)
• Message Processor (Text/Binary messages)
• PING/PONG Handler
• Base64 Encoder/Decoder
• SHA1 Handler
• UTF8 Validator
┌─────────────────────────────────────────────┐
• Application Layer │
• (User Implementation: onopen/close/message) │
• ┤
• wsServer Library │
• ┌─────────────┐ ┌─────────────┐ │
• Event │ │ Connection │ │
• Handler │←→│ Manager │ │
• ┘ └─────────────┘ │
• ┌─────────────┐ ┌─────────────┐ │
• Frame │ │ Protocol │ │
• Processor │←→│ Handler │ │
• ┘ └─────────────┘ │
• ┤
• Socket Layer │
• ┘
Important Details to Highlight
a) Thread Management:
• How each client connection gets its own thread
• Thread pool management system
b) WebSocket Protocol Flow:
• Handshake process
• Frame processing
• Message handling
• PING/PONG mechanism
c) Integration Points:
• How user callbacks (onopen, onclose, onmessage) integrate
• External interface points (ws_socket, ws_sendframe functions)
Implementation Details
• src/ws.c as the core implementation
• src/handshake.c for connection establishment
• src/base64.c and src/sha1.c for protocol requirements
• src/utf8.c for message validation