-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ReactiveStreams and Java 9 Flow API support #53
Comments
@hantsy we definitely want to supporting other options than just My only suggestion is that I guess we could have multiple (A tangential issue is that we also need to support reactive database drivers other than the ones Vert.x provides.) |
That is something we need to discuss. if we go for Mutiny CC @cescoffier instead of CompletionStage, then Mutiny has bridges tot he other types and is an implementation of ReactiveStreams (for Publisher at least). |
Note that this is now a very easy thing for a user to contribute. |
I agree with @emmanuelbernard :-) |
@cescoffier I already implemented a Mutiny-based API. It's documented in the readme and in the example program. |
Cool! I will have a look! |
Alright, so from what I can see here: https://smallrye.io/smallrye-mutiny/ The
I don't know anything at all about this, but it also seems to be ReactiveStreams, so perhaps that's covered too. Anyway, we're targeting Java 8 for good reasons so we can't do anything specific with this API right now. Look, I'm going to close this issue, since it's simply a bit too open ended. Once someone has some real concrete use-case-driven experience, they can open new issues to request specific new APIs. Right now I can't see what code I could possibly write that would let me mark this issue as "done". (Or rather, I probably already wrote the code when I added |
Please add ReactiveStreams(rxjava2, reactor, MP ReactiveStreams etc)and Java 9 Flow API support.
it could be designed like the
.rx()
method of JAXRS client, provide variants toopenRxSession(<accept a impl type>)
.The text was updated successfully, but these errors were encountered: