Pavel,
I highly appreciate your work and understand that the EG is expected to provide results fast.
But see, Oracle stalled work of this EG for months (see the long pauses in the mailing list), so some EG members, just like me, might need short time to remember the discussions and the outcome.
So I think it would be fair if Oracle could first recap what the EG decided already and what points are still to be discussed. In fact, I can remember a lot of discussion, but not any kind of formal agreement upon _any_ of the items you mentioned.
Besides that, I appreciate your plan and in particular like the idea of going through the issue tracker to address smaller items, too.
Thanks
-Markus
-----Original Message-----
From: Pavel Bucek [mailto:pavel.bucek_at_oracle.com]
Sent: Mittwoch, 11. Januar 2017 22:17
To: jsr370-experts_at_jax-rs-spec.java.net
Subject: JAX-RS 2.1 - work schedule
Dear experts,
thanks for your warm welcome!
Let's kick this off with the work schedule. As mentioned in the renewal ballot, we have following three big features we want to deliver:
- Reactive client API
- Server Sent Events support (server and client)
- Non-blocking I/O
Since we already have proposal for the first two, I believe we should start with them - to finish them off and then continue with non-blocking I/O.
As Santiago mentioned, the schedule is pretty aggressive and we need to see how fast this will go. After we are done with these "bigger" tasks, we will go through backlog items, fitting as much as we can into this release.
So what's going to happen next? We are currently working in PoC implementation of Reactive client API which is currently in the JAX-RS source repository master branch - it is almost ready for review. We identified small improvement needed there and I'm going to take care of that, finish the PoC implementation and document the API on the wiki.
Once this is done, I'll send a request for review to this mailing list.
Please let us know if you have any comments, questions or suggestions.
Thanks and regards,
Pavel