Re: WebSocket client API

2015-10-06 Thread Pavel Rappo
Hi, Here's an update on the WebSocket API. This iteration tries to address all issues have been discussed so far: webrev: http://cr.openjdk.java.net/~prappo/8087113/webrev.01/ javadoc: http://cr.openjdk.java.net/~prappo/8087113/javadoc.01/ Main differences from the previous version: *

RFR: JDK-8022748 (new URI(u.toString()).equals(u), does not hold with paths containing colons

2015-10-06 Thread Sebastian Sickelmann
Hi, i investigated the problem described in JDK-8022748[1] i found that the parser needed to be rescued for confusion while handling relative URIs. A URI created through the relativize-method is schemaless and so it need to handle the special-case (a colon in the path-element). While there is al

Re: TLS ALPN Proposal v7

2015-10-06 Thread David M. Lloyd
I didn't reply on this last week, but this looks workable to me. Thanks! On 10/02/2015 07:19 PM, Bradford Wetmore wrote: On 10/1/2015 7:35 PM, Xuelei Fan wrote: On 10/2/2015 9:03 AM, Bradford Wetmore wrote: Major changes: 1. ApplicationProtocols is gone. The H2 black list and comparator

Re: WebSocket client API

2015-10-06 Thread Paul Sandoz
Hi, Overall i think this API seems to be compressing down nicely to a small number of classes/interfaces, but i still think there is some room for further simplifications. WebSocket I don’t see the need for a context parameter. Context can be obtained via capturing. That reduces the requirem