Skip to content
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

support additional async return types #219

Closed
Ladicek opened this issue Apr 20, 2020 · 4 comments
Closed

support additional async return types #219

Ladicek opened this issue Apr 20, 2020 · 4 comments
Assignees
Milestone

Comments

@Ladicek
Copy link
Contributor

Ladicek commented Apr 20, 2020

We should support additional asynchronous return types, in addition to just CompletionStage. That is:

  • Mutiny: Uni
  • RxJava: Single, Maybe, Completable
  • Reactor: Mono

We can probably ignore stream types (Multi, Observable/Flowable, Flux) for now.

@Ladicek
Copy link
Contributor Author

Ladicek commented Apr 20, 2020

See also #218 (comment)

@schulzp
Copy link

schulzp commented Jun 24, 2020

Hi @Ladicek!

I'd highly appreciate support for Uni and the like. It would save us the @Asynchronous overhead as we're already using Vert.X' asynchronous web client. Is this part of any roadmap, already?

@Ladicek
Copy link
Contributor Author

Ladicek commented Jun 24, 2020

Hi @schulzp, I think what you're after is #218. This issue is just about allowing different return types for @Asynchronous methods. (Actually perhaps you want a combination of both :-) )

If you care about not having to use @Asynchronous, or more generally about its semantics of "always run this on an extra thread", you can comment on #218 and also on eclipse/microprofile-fault-tolerance#533 -- hearing from community folks would be very good.

As for roadmap, unfortunately there's none at the moment, as I have very little time to spare on SmallRye Fault Tolerance :-(

@Ladicek
Copy link
Contributor Author

Ladicek commented Nov 4, 2020

Done in #310.

@Ladicek Ladicek closed this as completed Nov 4, 2020
@Ladicek Ladicek self-assigned this Nov 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants