Nathan Miles
Nathan Miles
The main issue with doing this is that there just isn't a mechanism in Java to do async lookups. Netty has resolvers that will hit DNS servers in an async...
The APIs are there in Linux and Windows at the OS layer, yes. But I don't believe those APIs exist on all OSes that Java supports, so there is not...
If you figure out how to do non-blocking DNS lookups using the OS mechanism on the JVM please tell me how you did it
AHC does not support HTTP2
Am I interpreting this correctly in thinking that you're blocking a Netty thread on purpose?
This seems like a pretty big API change and a complex internal change just because we want to use `InflightNameResolver`. The only thing preventing us from using `InflightNameResolver` is that...
I haven't noticed it if it has. We have retry logic on everything so small blips usually get absorbed without issue.
[Your test server is blocking the event loop.](https://github.com/Mark0Sertic/async-http-client-test/blob/3ea625abbd1fc447f50e679a6b0aaf597312adbc/src/main/java/com/example/demo/service/FetchServiceImpl.java#L14) So your server is only able to serve one request at a time.
Couldn't tell ya. If I had to guess, I'd guess something on your server's side treats that differently and puts those requests on different threads. This is an issue with...
This is a really wild bug and I'm pretty surprised that this hasn't been fixed. This is very disruptive, and seems like a huge security issue. Is there any ETA...