On Sat, 21 Nov 2020, Daniel Stenberg wrote:
> > Are you OK with the simple "+" version?
>
> Absolutely.
Cool. Then we'll make a PR once we're done.
Thanks,
Paul
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you ar
On Thu, 19 Nov 2020, Groke, Paul wrote:
Are you OK with the simple "+" version?
Absolutely.
--
/ daniel.haxx.se
| Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support, ports, new features
| https://www.wolfssl.com/contact/
--
> On Wed, 18 Nov 2020, Tomalak Geret'kal wrote:
> Personally, I'd go with:
>
> host:port:
> -host:port:
> and the new
> +host:port:
>
> Though either kind of entry can ultimately be removed with "-", an explicit
> "+" feels like an action ("add this mapping to the expireable cache"),
>
On 18/11/2020 15:05, Groke, Paul via curl-library wrote:
> On Wed, 18 Nov 2020, Daniel Stenberg wrote:
>
>> Exactly how to extend the format can of course be further discussed. I think
>> I would prefer a slighly more descriptive text, like perhaps ":temp" - and
>> we could then introduce that ex
On Wed, 18 Nov 2020, Daniel Stenberg wrote:
> Exactly how to extend the format can of course be further discussed. I think
> I would prefer a slighly more descriptive text, like perhaps ":temp" - and we
> could then introduce that extra field for further instructions if we want to
> later on.
>
On Wed, 18 Nov 2020, Groke, Paul via curl-library wrote:
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.
I would suggest adding an additional recognized prefix for the
CURLOPT_RESOLVE string
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 tr
