mirror of
https://github.com/warmcat/libwebsockets.git
synced 2025-03-23 00:00:06 +01:00
![]() In some cases devices may be too constrained to handle JSON policies but still want to use SS apis and methodology. This introduces an off-by-default cmake option LWS_WITH_SECURE_STREAMS_STATIC_POLICY_ONLY, if enabled the JSON parsing part is excluded and it's assumed the user code provides its policy as hardcoded policy structs. |
||
---|---|---|
.. | ||
minimal-secure-streams | ||
minimal-secure-streams-alexa | ||
minimal-secure-streams-avs | ||
minimal-secure-streams-client-tx | ||
minimal-secure-streams-metadata | ||
minimal-secure-streams-policy2c | ||
minimal-secure-streams-proxy | ||
minimal-secure-streams-seq | ||
minimal-secure-streams-sink | ||
minimal-secure-streams-staticpolicy | ||
README.md |
Secure Streams
Secure Streams is a client API that strictly decouples the policy for connections
from the payloads. The user code only deals with the stream type name and payloads,
a policy database set at lws_context
creation time decides all policy about the
connection, including the endpoint, tls CA, and even the wire protocol.
name | demonstrates |
---|---|
minimal-secure-streams | Minimal secure streams client / proxy example |
minimal-secure-streams-tx | Proxy used for client-tx test below |
minimal-secure-streams-client-tx | Secure streams client showing tx and rx |