-
## Description
Right now the only way to access the SMTP data is to issue a blocking `get` request on the future. This blocks threads defeating the purpose of the non-blocking client in the f…
-
### Is your feature request related to a problem?
Current Transport Request calls to OpenSearch are synchronous, a better way will be to make them asynchronous if in them future we want to make paral…
-
## Actual behavior
https://github.com/Spikhalskiy/java-sdk/commit/40c0d626e0ea4778a956e388d33754e67bde23a8#diff-7cfba47d2337ff3ee746b09a4d916e5e839f9b8bff45a26e588727667437c160R94
```
@Test
…
-
Hi,
I am reporting this observation that came up when we noticed our instances getting OOM killed.
This happens in any sort of loop, if the future completes instantly, no issue, but if it enters…
-
The request for this would be
a Post to "/data/register"
with parameters
"username"
"email"
"password"
-
**Type**: Feature
**Is your feature request related to a problem? Please describe.**
No, It's not.
**Describe the solution you'd like**
In order to create a new listener, the method defined mu…
-
First of all I really appreciate the work that people did here. I really liked the concept of completable future and was going to replace all my AsyncResult callbacks with VertxCompletableFuture, but …
-
Hello,
I had a question regarding the project.
The problem I've encountered with Vert.x and using CompletableFutures is you have to be very explicit about which ThreadPool (EventLoop vs. WorkerThr…
-
Suppose I have a large codebase using j4rs, with calls to jvm::invoke_async. I don't want to audit every single call site to ensure the returned future is `CompletableFuture`. You should consider disa…
-
https://spring.io/guides/gs/async-method/
https://geowarin.github.io/completable-futures-with-spring-async.html