You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on a simple implementation of the dns module in #825, I received an interesting comment.
This should reuse the DNS resolver we added for llrt_http. Probably need to split a lib crate. Originally posted by @Sytten in #825 (comment)
I am struggling with how to proceed with the integration, so I would like to discuss this here.
Should the results obtained from either fetch() or dns.lookup() be stored in the CachedDnsResolver?
fetch() already reuses CachedDnsResolver results, but should dns.lookup() also reuse CachedDnsResolver results?
For actual DNS name resolution, should I use toklo::net::lookup_host() or dns_lookup:lookup_host()? At least, dns_lookup:lookup_host() seems to behave the same as OS name resolution and also refers to /etc/hosts. I don't know about tokio's.
If my thinking is fundamentally flawed, please feel free to point it out. :)
The text was updated successfully, but these errors were encountered:
toklo::net::lookup_host() should be used. AFAIK they both lower level syscalls/libc to perform the lookups. We can then remove the dns_lookup dependency
While working on a simple implementation of the dns module in #825, I received an interesting comment.
I am struggling with how to proceed with the integration, so I would like to discuss this here.
fetch()
ordns.lookup()
be stored in theCachedDnsResolver
?fetch()
already reusesCachedDnsResolver
results, but shoulddns.lookup()
also reuseCachedDnsResolver
results?toklo::net::lookup_host()
ordns_lookup:lookup_host()
? At least,dns_lookup:lookup_host()
seems to behave the same as OS name resolution and also refers to/etc/hosts
. I don't know about tokio's.If my thinking is fundamentally flawed, please feel free to point it out. :)
The text was updated successfully, but these errors were encountered: