I don't think it should run when the option is set only because it would be surprise in which order things are done, and it might matter when the handle is added or not to handles or shared objects.

The different list or not question is of course a matter of how the exact implementation is done. It can be done in several different ways. Consideration needs to be made so that repeated use of a handle that has this list set works and that it works in the same defined way. The current approach that only adds names can just add the names and then forget them, but a solution that removes them again needs to be able to redo both operations on repeated use.

---
** [bugs:#1431] removing names from DNS cache with CURLOPT_RESOLVE is not implemented**
**Status:** open-confirmed
**Labels:** dns memory leak 
**Created:** Tue Oct 07, 2014 09:19 AM UTC by ygrek
**Last Updated:** Thu Oct 23, 2014 11:00 PM UTC
**Owner:** Daniel Stenberg
Removing names from DNS cache with CURLOPT_RESOLVE is not implemented (see TODO in Curl_loadhostpairs). With the fix 31860ab for https://sourceforge.net/p/curl/bugs/1327/ it means that constantly adding and deleting hostcache entries with CURLOPT_RESOLVE creates a memory leak, as such entries are never removed (nor by request nor automatically).
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.