Re: JEP 110: leeway for API changes?

2016-05-23 Thread Michael McMahon 

Hi,

API changes are still possible. Sorry, I haven't gotten around
to replying to all feedback, but I will do this week.

Thanks
Michael

On 19/05/16 15:02, Simone Bordet wrote:

Hi,

On Thu, May 19, 2016 at 3:54 PM, Anthony Vanelverdinghe
 wrote:

Hi

With the JDK's "Feature Complete" milestone coming up next week: how much
leeway is there still for API changes? I've made API suggestions (a.o. in
[1]), ranging from changing HttpResponse.multiProcessor::onStart's return
type (from BiFunction<..., Boolean> to BiPredicate), to building on the
j.u.c.Flow API & eliminating HttpResponse.MultiProcessor. So I'm wondering
what's still on on the table for JEP 110 w.r.t. API changes?

I second that. I also made API change proposals, but no feedback.

Re: JEP 110: leeway for API changes?

2016-05-19 Thread Simone Bordet 
Hi,

On Thu, May 19, 2016 at 3:54 PM, Anthony Vanelverdinghe
 wrote:
> Hi
>
> With the JDK's "Feature Complete" milestone coming up next week: how much
> leeway is there still for API changes? I've made API suggestions (a.o. in
> [1]), ranging from changing HttpResponse.multiProcessor::onStart's return
> type (from BiFunction<..., Boolean> to BiPredicate), to building on the
> j.u.c.Flow API & eliminating HttpResponse.MultiProcessor. So I'm wondering
> what's still on on the table for JEP 110 w.r.t. API changes?

I second that. I also made API change proposals, but no feedback.

-- 
Simone Bordet
http://bordet.blogspot.com
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz

JEP 110: leeway for API changes?

2016-05-19 Thread Anthony Vanelverdinghe 

Hi

With the JDK's "Feature Complete" milestone coming up next week: how 
much leeway is there still for API changes? I've made API suggestions 
(a.o. in [1]), ranging from changing 
HttpResponse.multiProcessor::onStart's return type (from BiFunction<..., 
Boolean> to BiPredicate), to building on the j.u.c.Flow API & 
eliminating HttpResponse.MultiProcessor. So I'm wondering what's still 
on on the table for JEP 110 w.r.t. API changes?


[1] http://mail.openjdk.java.net/pipermail/net-dev/2016-March/009608.html

Kind regards,
Anthony