Re: RFR:8190843 can not set/get extendedOptions to ServerSocket

2017-12-02 Thread Chris Hegarty
> On 1 Dec 2017, at 07:13, vyom tewari wrote: > > Hi Chris, > > Thanks for review, while my testing i discovered issue in the way we handle > extended socket options and standard socket options. I fixed it and updated > one test as well. > > I removed one redundant "if check" which i think

Re: RFR:8190843 can not set/get extendedOptions to ServerSocket

2017-12-02 Thread Roger Riggs
+1 On 12/2/2017 4:17 AM, Chris Hegarty wrote: On 1 Dec 2017, at 07:13, vyom tewari wrote: Hi Chris, Thanks for review, while my testing i discovered issue in the way we handle extended socket options and standard socket options. I fixed it and updated one test as well. I removed one redun

Re: Parsing too strict in java.net.URI? (David Lloyd)

2017-12-02 Thread Peter Firmstone
Have there been any recent developments, updates, or insights on this issue? I wonder if a gradual change to RFC 3986 support might be more appropriate: for example, start with*just* accepting empty SSP. If the compatibility requirements of java.net.URI are too stringent to allow for any change