Hi, I want to propose to add a feature by which libcurl users can pre-populate DNS cache entries that will expire just like those added by libcurl itself. (We want to start using a shared DNS cache, and having the entries added by CURLOPT_RESOLVE remain in the shared cache forever could cause trouble in our application.)
I would suggest adding an additional recognized prefix for the CURLOPT_RESOLVE strings. Maybe a '?' or '+'. Would this be a welcome change? We'd be willing to implement this and provide a PR. Another idea would be to allow the user to specify an explicit TTL. We don't need this, and it would require more changes, so we'd prefer the simpler way of just providing the user to skip the "mark as permanent" part. But if you prefer a mechanism to specify an explicit TTL per entry, we'd also be OK with implementing that. Best regards, Paul Groke The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. Dynatrace Austria GmbH (registration number FN 91482h) is a company registered in Linz whose registered office is at 4020 Linz, Austria, Am Fünfundzwanziger Turm 20 ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
