mirror of
https://github.com/warmcat/libwebsockets.git
synced 2025-03-30 00:00:16 +01:00
![]() lws_ss_set_metadata can fail... eg, due to transient OOM situation... if it does, caller must take appropriate action like disconnect and retry. So mark the api as requiring the result checking, and make sure all the examples do it. |
||
---|---|---|
.. | ||
minimal-secure-streams | ||
minimal-secure-streams-alexa | ||
minimal-secure-streams-avs | ||
minimal-secure-streams-client-tx | ||
minimal-secure-streams-cpp | ||
minimal-secure-streams-hugeurl | ||
minimal-secure-streams-metadata | ||
minimal-secure-streams-metrics-proxy | ||
minimal-secure-streams-policy2c | ||
minimal-secure-streams-post | ||
minimal-secure-streams-proxy | ||
minimal-secure-streams-seq | ||
minimal-secure-streams-server | ||
minimal-secure-streams-server-raw | ||
minimal-secure-streams-sigv4 | ||
minimal-secure-streams-smd | ||
minimal-secure-streams-staticpolicy | ||
minimal-secure-streams-testsfail | ||
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 |