I'm in a single-threaded environment and validation can only be done by another process. Actual validation involves IPC, so it can only be async and must not be blocking.
Val -----Original Message----- From: Daniel Stenberg <[email protected]> Sent: Wednesday, February 12, 2020 11:45 PM To: Valerio Di Gregorio (vadigreg) <[email protected]> Cc: Valerio Di Gregorio (vadigreg) via curl-library <[email protected]> Subject: RE: Issues implementing an async certificate validation engine On Wed, 12 Feb 2020, Valerio Di Gregorio (vadigreg) wrote: > Thanks for your reply. I'm doing the cert verfication in the callback > and the operation is async. The way the async verification is achieved > is by using ASYNC_pause_job (which internally does a longjmp). > Callback won't return, because the async job gets paused. Once async > validation is done, SSL async job can resume. It's the resumed > callback that will finally return with a validation result. If the callback won't return until the verification is done (and you have a validation result), why do it async in the first place? What's the benefit? -- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://www.wolfssl.com/contact/ ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
