>> Maybe you could create handle pool? App would get handle from it or >> create new one if pool is empty, and returned handle to the pool instead >> of destroying it. > >Well, I will for sure look at the issue. >I can see that we partially re-use the handle. It's alive throughout the whole >incoming request, >which is handled by one thread. >Since we share almost nothing between the threads, it may be tricky to do so >now, but worth looking into.
Just to put this thread to rest: I ended up implementing CA-Bundle caching by myself and using CURLOPT_SSL_CTX_FUNCTION to inject it into the SSL context. Works like a charm. Switching the code to connection pooling is a nightmare in the current state of the code, so it'll have to wait, even though the connection phase is what dominates the profile at the moment. Thank you all for the comments. -- Jakub
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
