OK... So is this behavior by design? (getting an onRead notification when
there are no bytes available)
One more thing - I want to toggle the read flag back to "on" in the method
that sends the request. Can I get the key via the connectorHandler (or any
other way not in the onRead method)
Thanks,
Hagai.
--
View this message in context: http://www.nabble.com/newbie-question-about-blocking-ConnectorHandler.read-tp18474564p18531042.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.