Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Concurrency and send/recv
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Jacob Hoffman-Andrews via curl-library <curl-library_at_cool.haxx.se>
Date: Fri, 12 Mar 2021 20:45:10 -0800
Currently the rustls backend uses a buffer on the stack for its `send` /
`recv` implementations. I'd like to switch this to be a heap-allocated
buffer, initialized once and stored in the `connssl->backend` struct. Is it
guaranteed that `send` and `recv` are never called concurrently? In general
what are the concurrency properties that apply to TLS backends?
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2021-03-13
Date: Fri, 12 Mar 2021 20:45:10 -0800
Currently the rustls backend uses a buffer on the stack for its `send` /
`recv` implementations. I'd like to switch this to be a heap-allocated
buffer, initialized once and stored in the `connssl->backend` struct. Is it
guaranteed that `send` and `recv` are never called concurrently? In general
what are the concurrency properties that apply to TLS backends?
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2021-03-13