Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In Java NIO, it is easily understandable why a ServerSocketChannel must have a selector. The selector can check from among several client channels which is ready for I/O operations.
However, in some commentary I have read on the web, the selector mechanism is applied to the client SocketChannel. I don’t understand why a selector is of use to a client. Can anyone explain why it is of use in the usual circumstance where there is only one server?
Unless you’re connecting to hundreds of servers, it is difficult to see the point of non-blocking NIO in a client at all. But if you’re using non-blocking NIO, you definitely have to use a
Selector, otherwise you can’t know when to read the channel, or when it becomes writable again after an incomplete write.