Summary
Update websocket_facade to return i_protocol_client/i_protocol_server interfaces instead of messaging_ws_client/messaging_ws_server types. This aligns with the pattern already used by tcp_facade and udp_facade (PR #656).
What
- Create
ws_client_adapter implementing i_protocol_client
- Create
ws_server_adapter implementing i_protocol_server
- Update
websocket_facade.h return types
- Update dependent tests and samples
Why
Part of EPIC #577: Apply Facade pattern to reduce protocol header complexity.
- Reduces public API surface
- Provides unified interface across all protocols
- Enables protocol-agnostic client/server usage
Acceptance Criteria
Technical Notes
WebSocket is connection-oriented, so adapter implementation will be simpler than UDP.
Part of #577
Summary
Update
websocket_facadeto returni_protocol_client/i_protocol_serverinterfaces instead ofmessaging_ws_client/messaging_ws_servertypes. This aligns with the pattern already used bytcp_facadeandudp_facade(PR #656).What
ws_client_adapterimplementingi_protocol_clientws_server_adapterimplementingi_protocol_serverwebsocket_facade.hreturn typesWhy
Part of EPIC #577: Apply Facade pattern to reduce protocol header complexity.
Acceptance Criteria
websocket_facade::create_client()returnsi_protocol_clientwebsocket_facade::create_server()returnsi_protocol_serverTechnical Notes
WebSocket is connection-oriented, so adapter implementation will be simpler than UDP.
Part of #577