Andy Green 28ce32af64 client: secure streams ... 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.		2020-03-04 12:17:49 +00:00
..
client	client: secure streams	2020-03-04 12:17:49 +00:00
compression	cleaning	2020-01-05 22:17:58 +00:00
server	client: secure streams	2020-03-04 12:17:49 +00:00
header.c	cleaning	2020-01-05 22:17:58 +00:00
lextable-strings.h	rtos diet: http: remove headers at buildtime according to config	2020-03-04 11:00:04 +00:00
lextable.h	rtos diet: http: remove headers at buildtime according to config	2020-03-04 11:00:04 +00:00
minilex.c	rtos diet: http: remove headers at buildtime according to config	2020-03-04 11:00:04 +00:00
parsers.c	client: secure streams	2020-03-04 12:17:49 +00:00
private-lib-roles-http.h	rtos diet: http: remove headers at buildtime according to config	2020-03-04 11:00:04 +00:00