[
https://issues.apache.org/jira/browse/CXF-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15263006#comment-15263006
]
Sergey Beryozkin commented on CXF-6833:
---------------------------------------
It is still the early days, but from what I can see, on the server, the best we
can do is to have JAX-RS AsyncResponse which will be suspended while the client
is doing its own async calls. Observable subscriber will be notified once
Observable is finished and the Pair/etc of the data is available, and then
AsyncResponse will be resumed with this data to be returned to the client.
I may well be confused yet. Any chance you can prototype the way you see it
being utilized on the server ?
Right now I do see see what is expected in principle on the client side, and
I'm quite positive it can be aligned with JAX-RS 2.1 Reactive. The server one
is really about facilitating returning Observable final data...
> support RxJava Observable<T> in return values as a more composeable
> alternative to Future<T>
> --------------------------------------------------------------------------------------------
>
> Key: CXF-6833
> URL: https://issues.apache.org/jira/browse/CXF-6833
> Project: CXF
> Issue Type: Sub-task
> Components: JAX-RS
> Reporter: james strachan
> Fix For: 3.2.0
>
>
> when invoking multiple REST services concurrently in a microservice kinda
> world it can be really helpful to use RxJava's Observable<T> so that you can
> easily compose concurrent asynchronous requests together.
> e.g. see this blog:
> http://joluet.github.io/blog/2014/07/07/rxjava-retrofit/
> Its basically about using RxJava's Observable<T> as the result type; which is
> a little like a Future<T> but can handle streams of values and is composable.
> It would be great to do this both on the client and server side; as a server
> may invoke multiple asynchronous back ends and return a composition of
> results etc.
> e.g.
> {code}
> @GET("/session.json")
> Observable<LoginResponse> login();
> @GET("/user.json")
> Observable<UserState> getUserState();
> {code}
> you can then use the Observable<T> composition methods to join / flatMap to
> compose multiple requests across different microservice invocations together
> with timeouts etc e.g. to compose the latest from 2 calls:
> {code}
> Observable.combineLatest(api.fetchUserProfile(), api.getUserState(),
> (user, userStatus) -> new Pair<>(user, userStatus));
> {code}
> and you're done! There's support for timeouts and other kinds of composition
> mechanisms too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
