Brent Cook wrote:
> @@ -246,14 +252,18 @@ An already existing socket can be upgrad
> .Fn tls_connect_socket .
> Alternatively, a secure connection can be established over a pair of existing
> file descriptors by calling
> -.Fn tls_connect_fds .
> +.Fn tls_connect_fds . Using
> +.Fn tls_connect_cbs , read and write callbacks can be specified to handle the
> +actual data transfer.
I think we need just a wee bit more documentation. payload is not the clearest
name. It sounds like connection data. I think cookie? Or cbarg? Is it
necessary to pass the tls context to the callback? I think that's unusual.
read callback should be more like:
ssize_t (*read_cb)(void *buf, size_t buflen, void *cbarg);
