mirror of
https://github.com/warmcat/libwebsockets.git
synced 2025-03-16 00:00:07 +01:00
28ce32af64
Secure Streams is an optional layer on top of lws that separates policy like endpoint selection and tls cert validation into a device JSON policy document. Code that wants to open a client connection just specifies a streamtype name, and no longer deals with details like the endpoint, the protocol (!) or anything else other than payloads and optionally generic metadata; the JSON policy contains all the details for each streamtype. h1, h2, ws and mqtt client connections are supported. Logical secure streams outlive any particular connection and supports "nailed-up" connectivity regardless of underlying connection stability. |
||
|---|---|---|
| .. | ||
| minimal-secure-streams | ||
| minimal-secure-streams-alexa | ||
| minimal-secure-streams-avs | ||
| minimal-secure-streams-client-tx | ||
| minimal-secure-streams-proxy | ||
| minimal-secure-streams-seq | ||
| minimal-secure-streams-sink | ||
| 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 |