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
Integration of Qute and Mutiny #7101
Conversation
…d by Mutiny Also remove the SmallRye Reactive Streams Operators dependency - not required anymore.
Uni<String> uni = Uni.createFrom().completionStage(() -> template.data("name", "neo").renderAsync()); | ||
---- | ||
|
||
In this case, the rendering only starts once the subscriber requests it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like it's the same in both cases? Or did I misunderstand something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you use a renderAsync()
the rendering process starts even if you don't have anyone listening / prepared to receive the output. With Uni or Multi, it would only start if someone is there to receive it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me but I'll let @mkouba have the final say on this one.
This PR is part of the #7097 epic. It re-implement the reactive support of Qute to use Mutiny instead of RX: