Using OP_CONNECT with Selector.select causes selector to fire repeatedly

Deven You youdwei at linux.vnet.ibm.com
Wed Jan 9 21:52:54 PST 2013


Hi Alan,

Any suggestion about this webrev[1]?

[1] http://cr.openjdk.java.net/~youdwei/ojdk-317/webrev.02/ 
<http://cr.openjdk.java.net/%7Eyoudwei/ojdk-317/webrev.02/>

Thanks a lot!
On 11/23/2012 04:05 PM, Deven You wrote:
> Hi All,
>
> I just made a new java doc change[1] for this problem, could you take 
> a look and give your suggestions so we may improve it.
>
> [1] http://cr.openjdk.java.net/~youdwei/ojdk-317/webrev.02/ 
> <http://cr.openjdk.java.net/%7Eyoudwei/ojdk-317/webrev.02/>
>
> Thanks a lot!
> On 06/20/2012 03:41 PM, Alan Bateman wrote:
>> On 20/06/2012 08:21, Deven You wrote:
>>> Hi Alan and Jonathan,
>>>
>>> I have tried modifying the Selector.select() javadoc[1] so that 
>>> users can get clear information about the behavior of dealing with 
>>> OP_CONNECT.
>>>
>>> Could you or any one else take a look at review it.
>> I'm really busy at the moment and do not have time to spend on this. 
>> It will mostly likely require updates to Selector and SelectionKey's 
>> class description, a note in SocketChannel connect might be useful too.
>>
>> -Alan.
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/nio-dev/attachments/20130110/157a1c35/attachment.html 


More information about the nio-dev mailing list