On Mon, 25 Apr 2022, Dmitry Karpov wrote:
So, as far as documentation is concerned, I was envisioning that this
feature will be documented as "opaque resolver code, which meaning depends
on the used resolver backend". Because this is a debugging feature, there is
no need to document more in libcurl, and the application developers can look
it up in the resolver code and provide a better information/description if
needed.
Shouldn't that value then rather just get shown with an infof() call?
Whatever we provide in a value in an API we *know* that someone will write an
application that assumes that we will provide the same value for the same
action even in the future. Unless we add a randomizer to it on purpose to
prevent it from ever being a fixed number, but then we also remove the utility
of it I guess.
--
/ daniel.haxx.se
| Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support, ports, new features
| https://curl.se/support.html
--
Unsubscribe: https://lists.haxx.se/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
