[jax-rs-spec users] Re: Reactive Client API

From: Pavel Bucek <>
Date: Mon, 23 Jan 2017 18:32:08 +0100

Hi Sergey,

sorry, that was maybe unfortunate wording on my side, sorry for that.

You definitely haven't lost your chance to provide feedback. I just
wanted to state that for now, I'd like to move on to other issue. Maybe
slightly more aggressively than needed.

As you all know, we have limited timeframe, which cannot be extended. I
don't want to discuss the reason for that limitation - I don't think
that will lead anywhere and we will loose even more time.

Client Rx API and SSE was there for a while now, you can see that
original proposals were brought up a while ago (see [1]) and I'd like to
finish them soon. I'm slightly worried about Non-blocking I/O, since
that part of the proposal is by far the least complete and I suspect
that we'll need much more time to discuss that compared to Client Rx and

I hope that cleared up your concern little bit. I always appreciate any
feedback from anyone and I'll evaluate it as soon as possible, but we
also need to pay attention to the schedule. (There is always an option
to drop something in favor of spending more time on the rest, but I
don't want to go that way if not necessary).

Best regards,


On 23/01/2017 18:12, Sergey Beryozkin wrote:
> 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