Hi all,
I wonder if it would be possible to add a new public exception time for the
situation of an SocketChannel.accept(…) or SocketChannel.open(…) (and the same
for ServerSocket / Socket) failing because of too many open files.
The reason is because especially when acting as a server such an
Hi,
updated webrev. May I have a reviewer to review this
http://cr.openjdk.java.net/~xiaofeya/8043838/webrev.01/
-Felix
On 2016/12/5 15:50, Felix Yang wrote:
On 2016/12/5 15:47, Langer, Christoph wrote:
Hi Felix,
looks ok to me.
You probably should remove the reference to the old shell
On 12/05/2016 06:29 AM, Norman Maurer wrote:
Hi all,
I wonder if it would be possible to add a new public exception time for the
situation of an SocketChannel.accept(…) or SocketChannel.open(…) (and the same
for ServerSocket / Socket) failing because of too many open files.
The reason is beca
> Am 05.12.2016 um 18:48 schrieb David M. Lloyd :
>
>> On 12/05/2016 06:29 AM, Norman Maurer wrote:
>> Hi all,
>>
>> I wonder if it would be possible to add a new public exception time for the
>> situation of an SocketChannel.accept(…) or SocketChannel.open(…) (and the
>> same for ServerSock
Hello,
I know it is a radical idea, but what about exposing errno value in an
IOException.
I do think that the new ConnectionRefused subtype is helpful, but for each
seldomly occuring error case a dedicated exception is more work than a one time
mapping of native errormcodes to fields.
Gruss
B
Hi,
I just want to confirm the plans for the HTTP client API in JDK 9 that
were hinted at previously. There is a new feature called "incubator
modules" which has just been proposed for JDK 9. The idea is to
accommodate new APIs in JDK which are not quite ready to be standardized
as part of Ja
Add core-libs.
Thanks,
Felix
On 2016/12/5 22:14, Felix Yang wrote:
Hi,
updated webrev. May I have a reviewer to review this
http://cr.openjdk.java.net/~xiaofeya/8043838/webrev.01/
-Felix
On 2016/12/5 15:50, Felix Yang wrote:
On 2016/12/5 15:47, Langer, Christoph wrote:
Hi Felix,
looks
