Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate c-ares with the runtime #3120

Closed
brson opened this issue Aug 7, 2012 · 4 comments
Closed

Integrate c-ares with the runtime #3120

brson opened this issue Aug 7, 2012 · 4 comments
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Milestone

Comments

@brson
Copy link
Contributor

brson commented Aug 7, 2012

c-ares is for async DNS, and until now has been included in libuv. They have recently decoupled libuv and c-ares so we will need to do that work ourselves.

joyent/libuv#518

@graydon
Copy link
Contributor

graydon commented Aug 29, 2012

Strange. I don't get it. Does node still do DNS? Did they just move the binding up a level or something?

@brson
Copy link
Contributor Author

brson commented Aug 29, 2012

Yes. Node is responsible for using c-ares now.

@mitsuhiko
Copy link
Contributor

c-ares is too buggy from my experience and it does not use the operating system's dns caches. libuv by default just keeps a background thread for such cases and does the lookup in that one. Unless that implicit thread is a problem I think that's a much more reasonable idea.

@pcwalton
Copy link
Contributor

Closing per @mitsuhiko's comment, reopen if this is still desired.

RalfJung pushed a commit to RalfJung/rust that referenced this issue Oct 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Projects
None yet
Development

No branches or pull requests

4 participants