This content has been marked as final. Show 3 replies
this would block if/when the socket write buffer filledNo, it would return zero from the write.
1) Is my basic approach of only setting OP_WRITE when I have data to send correct?That's one way. The other way is just do the write and only set OP_WRITE if & when you get the zero return.
2) What am I missing with regards to unblocking the Selector.select() when I modify the interestOP values.If you're doing this in a separate thread from the selector thread, it will block on an internal synchronization, so you need to wakeup() the selector thread first and code its selector loop such that it won't get back around to the select() until your OP_WRITE set/reset is done: these methods need to synchronize on the selector. The selector won't react to the new values of interestOps() until the next select() invocation anyway.
Thanks EJP. I missed altogether the fact that the write would return zero! Shows I still am not thinking in non-blocking terms.
I am setting OP_WRITE outside of the selector thread and last night while reading your book again I came to understand that I needed to wakeup() the selector thread. I was wrongly assuming that key_.interestOps(newOps) would do the wakeup(). Looks like my present design needs tweaking to allow access to the selector. Maybe another 20 or so reads of 4.6.2 will help me.
Edited by: sabre150 on May 2, 2012 7:00 AM
:-) I have just re-read the Javadoc for Selector and it is all in there! No design change is needed since the key has a reference to the Selector!
Edited by: sabre150 on May 2, 2012 7:10 AM
So with the addition of two identical lines of code my server now basically works (well it does not actually fall over and the tunnel transfers stuff). I now have to worry about how to close it properly!