Julien Ponge
Julien Ponge
We might chat about that with @alesj next week then
@doppelrittberger yes if you have a PR it's always useful to make progress 👍
Note: `expecting` is a method for Vert.x `Future`, but since we wrap `Future`-returning methods to `Uni`, this requires further investigations.
/cc @vietj @cescoffier
To support cases like https://vertx.io/docs/apidocs/io/vertx/core/http/HttpResponseExpectation.html we'd need: - a generator of Mutiny (or Rx, same issue) APIs wrapping, say, `HttpResponseExpectations` that is get called on build (hard-coded paths, but at...
Rx PR https://github.com/vert-x3/vertx-rx/pull/317
The issue is that it will indeed block, perhaps not for long, but for sure the thread will be blocked, and if it's an event-loop thread it's a bigger issue....
It looks like this: https://github.com/smallrye/smallrye-mutiny/blob/main/implementation/src/main/java/io/smallrye/mutiny/operators/multi/MultiEmitOnOp.java#L155 The idea is that you use an `AtomicInteger` to track concurrent requests. The first thread who bumps it to `1` does the work, the other...
This will limit concurrency though (because 1 worker thread needs to await until ready)
The tricky part seems to be the busy wait loop. I wouldn't use Mutiny itself, but you can use the executor service from its `Infrastructure` class: https://javadoc.io/static/io.smallrye.reactive/mutiny/2.8.0/io.smallrye.mutiny/io/smallrye/mutiny/infrastructure/Infrastructure.html#getDefaultWorkerPool() The busy wait,...