
Radikant WebSocket is a simple, cross-platform C “shim" that provides a simple and consistent API for WebSockets.
Radikant WebSocket is a simple, cross-platform C library that provides a simple API driving WebSockets. It offers both synchronous and asynchronous interfaces. It uses Radikant Socket, and Radikant TLS to establish a connection in either server of client mode.
Currently only the client is usefull, because Radikant TLS, Radikant Socket and Radikant Event must be refactored to a more sane and scalable architecture to provide better decoupling for async server capabilities and mulitple client handling.
These libraries currently follow anti-patterns. Most likely some kind of top level orchestration layer needs to be created (possibly Radikant-Connect-C that uses these low-level drivers as pure state machines but orchestrates with clear responsibilities and seperation of concerns.
For example i’m researching how to handle mulitple WebSockets clients in a server context, Where should this be managed? In TLS, socket or WebSocket? Should we use use Radikant Event or create a smaller event only lib.