zekronium

I think in quite a few cases for different uses "rotating" your proxy might come in handy even on the same host. The way it is now its impossible to...

Hash code check might not suffice for this to work properly. Due to copied objects of the proxyOptions, even while applying the same proxy it can produce a different hashcode...

I get the same issue both of self hosted and not (windows-latest in both cases) What happens to me is, cache gets restored perfectly fine if I use the same...

Have you ever tested how this behaves on NIO eventloop environments, technically the method/thread/object is never blocked since its monitoring the Selector for IO, so I assume this would fall...

Its not entirely an issue, atleast I dont know if it is. Hence why I asked your opinion on how do you think it might behave and if there might...

This has been fixed by another PR, I assume safe to close?

> I also encountered this problem before. > In order to fix it, I had to extend **CompletableFuture** and reimplement **thenCompose()** and **complete()**. What changes did you have to make?

Does this apply to `internal-blocking-threads` the same way?

In the talk they communicated that one of the big penalties in too many threads is the cost of thread wakeup. This could impact throughput initially while handshaking SSL since...

With this as is, impossible to use new adaptive allocator too. @franz1981 this might affect quarkus too Context: https://github.com/netty/netty/pull/13976