Julien Viet

imho just await is fine, CompletionStage has other purpose and CountDownLatch is a read/write interface (i.e if you have it you can count() and (which is what flag() does more...

we could think of Checkpoint to be a class an extend the latch, I'm not sure it would buy anything as it's quite a minimalistic API.

it was not clear if you meant about API reuse or code reuse it would be great also to clarify that await should throw an exception when the context fails...

you can call it awaitSuccess :-)

such project could have their Options extend or embed a NetClientOptions data object

it would be great to have a more official support for Kotlin in Vert.x using the code generation. I'm particularly thinking into the upcoming coroutine support for Kotlin (I've implemented...

have you tried the new Vert.x gRPC implementation ? I believe it should work.

I think we could resolve the origin server before the interceptors kick-in and then it would be exposed in the ProxyContext and can be overriden, or something like that .

sometimes the ProxyContext is not available for a resolution, e.g in the WebSocket case, so we need to come with an interface that provides similar info for this case

can you provide a reproducer test ?