5 commits

Author	SHA1	Message	Date
Andy Green	85dc0883a2	ss: handle rx and tx return values properly ... You can disconnect the stream by returning -1 from tx(). You can give up your chance to send anything by returning 1 from tx(). Returning 0 sends `*len` amount of the provided buffer. Returning <0 from rx() also disconnects the stream.	2020-05-04 14:36:39 +01:00
Andy Green	84f8bdc3d8	ss: support metadata string expansion in endpoint string ... This lets you set metadata symbols exposed by the streamtype policy into the endpoint address. No ABI change	2020-03-16 16:56:11 +00:00
Andy Green	28c0e51cd6	client: unify post tls accept handling	2020-03-07 20:20:07 +00:00
Andy Green	9695e23c00	ss: mqtt: add will and other sundries to policy ... Replace the hacked-in constants with policy entries for sundry MQTT features, and add to the policy readme.	2020-03-04 12:17:49 +00:00
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