Channel.isWritable()

[gonzus]

jasons2645 wrote:
> 
> In both of these cases, the server would send data for a while and then
> stop.  After further investigation, I discovered that the server had
> written more data to the wire than the client had read off the wire.  It
> was as if the client needed more chunks before it would notify its
> ChannelHandler that a message had arrived.  Sure enough, when I modified
> approach (1) above so that the server waited for up to 300ms, then sent
> the data anyway, the code worked (although rather slowly, since there are
> occasional 300ms hiccups).
> 

This might be a result of Nagle's algorithm. You could try doing a

    bootstrap.setOption("tcpNoDelay", true);

on your channel. But I think you will need a deeper answer than this one in
order to answer your requirements.

Best regards.
-- 
View this message in context: http://n2.nabble.com/Channel.isWritable%28%29-tp3068932p3069027.html
Sent from the Netty User Group mailing list archive at Nabble.com.