Download
Browse source Changelog
Documentation
Project   Bug Bounty   Help us   Known bugs   TODO Protocols   CA bundle   HTTP Cookies   HTTP/2   SSL Certs Releases   Security   Version numbers   Vulnerabilities curl tool   man page   Tutorial   HTTP scripting Who and Why
libcurl
ABI API Competitors Examples Features Mailing list Related libs Using libcurl Tutorial Testimonials
Get Help
curl-library curl-users Mailing lists Book: Everything curl Video presentations Report a bug Paid support
Development
Autobuilds Code Style Contribute Deprecate Internals Release Notes Release Procedure Roadmap Run Tests Security Process Specifications Test curl
News
Changelog Release table
curl / Mailing Lists / curl-users / Single Mail
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.

RE: Issues implementing an async certificate validation engine

From: Valerio Di Gregorio \(vadigreg\) via curl-users <curl-users_at_cool.haxx.se>
Date: Tue, 11 Feb 2020 16:56:02 +0000

Hello Daniel,
Thanks for your reply. I will post this on curl-library. Sorry for polluting this mailinglist.

Unfortunately I'm single-threaded so I must avoid any

-----Original Message-----
From: Daniel Stenberg <daniel_at_haxx.se>
Sent: Tuesday, February 11, 2020 5:50 PM
To: Valerio Di Gregorio (vadigreg) via curl-users <curl-users_at_cool.haxx.se>
Cc: Valerio Di Gregorio (vadigreg) <vadigreg_at_cisco.com>
Subject: Re: Issues implementing an async certificate validation engine

On Tue, 11 Feb 2020, Valerio Di Gregorio (vadigreg) via curl-users wrote:

> Is there a reliable way (only when data is really ready) and a prompt
> way (in order of micro/milli-seconds) to wake up from ASYNC_pause_job()?

This is the mailing list for the curl tool and related subjects. You're using the library so the curl-library list is probably a better fit.

But you're asking about behaviors in an OpenSSL call and then the curl-library mailing list isn't really the most suitable one either. I would propose the OpenSSL users mailing list for that, I think.

Then again, you probably don't have to use OpenSSL's fancy "async" stuff since you have to keep libcurl waiting in the callback anyway until you're done, so you *could* just bounce over the context pointer to your child thread, have it do whatever it needs to do, and then signal the callback thread again that it can go on... 

-- 
  / 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-users
Etiquette:   https://curl.haxx.se/mail/etiquette.html
Received on 2020-02-11