We're doing another @rustlang live-coding session on Saturday at noon EST! This time we'll *use* futures + tokio to make our ec2 crate fully asynchronous (it shouldn't be as focused on futures internals as the last one). Come join us :Dhttps://twitter.com/Jonhoo/status/977662091724296192 …
-
-
What are you using for dns lookups? I have a biased opinion for one ;)
1 reply 0 retweets 0 likes -
Not sure what you mean? There's no need for explicit DNS lookups since the AWS API gives us IP addresses directly :)
1 reply 0 retweets 0 likes -
Ah. I may have misunderstood the layer in which you’ll be working... I’ll look deeper into the rusoto library :)
1 reply 0 retweets 0 likes -
AFAIK, rusoto uses hyper, which internally has some dns stuff. I think that's where any dns magic you have in mind would fit!
1 reply 0 retweets 0 likes -
I’m pretty sure that uses std::net for DNS lookups which means that you’ll be blocking on name resolution. I’ll dig in.
1 reply 0 retweets 0 likes -
From memory there's a pool of threads named `hyper-dns` which presumably does that blocking dns stuff using futures-cpupool. https://github.com/hyperium/hyper/blob/5db85316a10d0b7bdd36524d85a746a23bd10190/src/client/connect.rs#L176 … is likely where to start. I'm sure they'd love async DNS!
1 reply 0 retweets 1 like -
Maybe also ping
@seanmonstar?1 reply 0 retweets 0 likes
The default connector does resolution with getaddrinfo in a pool of DNS threads. I'd love to change that to something like Trust DNS, if it doesn't include a dependency on a TLS implementation.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.