Re: RFR: 8189366: SocketInputStream.available() should check for eof

2018-10-17 Thread Chris Hegarty
On 12/10/18 12:58, Daniel Fuchs wrote: ...     int available = impl.available();     return eof ? 0 : available; addresses the issue of available potentially returning garbage after EOF while being much less risky... Agreed. The above resolves the original reported potential bug, without c

Re: RFR: 8189366: SocketInputStream.available() should check for eof

2018-10-17 Thread vyom tewari
sure, i will send the webrev  soon. Vyom On Wednesday 17 October 2018 04:31 PM, Chris Hegarty wrote: On 12/10/18 12:58, Daniel Fuchs wrote: ... int available = impl.available(); return eof ? 0 : available; addresses the issue of available potentially returning garbage after EOF wh