More specifically, your restarted the Reactive API discussion on Fri 13 January, which was 10 days back (incl 4 days of weekends). Given that and that it is m03, not m10, I'd say it is really too early IMHO to call it a mostly complete Reactive API even if it already looks good enough. Sorry if it sounds too pedantic
Thanks, Sergey
________________________________
From: Sergey Beryozkin <sberyozkin_at_talend.com>
Sent: 23 January 2017 17:12:57
To: jsr370-experts_at_jax-rs-spec.java.net
Subject: Re: Reactive Client API
Hi Pavel
Thanks for your effort.
I'm not happy though with the statement that there will be the higher
resistance. After Oracle blocking the work virtually for years it is now giving us a couple of
weeks per every theme to sort out everything ?
For ex, I can't afford spending 100% of my time on this work, have I lost a chance to provide some feedback now that SSE is on the map ? I'll have to run a m03 soon
enough against our code and then I'll provide a feedback re the reactive API.
As I said, I'm not sure I'll have anything to suggest on top of what is already available, but thought I'd raise the concern.
Thanks, Sergey
On 23/01/17 17:01, Pavel Bucek wrote:
> Dear experts,
>
> thank you for your inputs related to Reactive Client API. Seems like
> we reached the state, when we are ok with the outcome. That doesn't
> mean the API is final, but since we need to move on to other topics,
> there will be higher resistance in making significant changes in that
> area.
>
> Latest JAX-RS build (2.1-m03) contains the latest version of the
> proposal.
>
> Next on our list is support for Server Sent Events - I'll send a kick
> off email tomorrow.
>
> Thanks again for your cooperation and valuable feedback!
> Pavel
>