Incomplete writes

[Eugene]

thx for the answer, but having writes blocked should not be a problem. in
fact, I'm trying to block writer with if (!ch.isWritable()) return; and then
resume in channelInterestChanged. The issue i'm trying to understand - why
client never get last records. In my tests server trying to write fixed
amount (5000) of relatively small records (about 175 bytes each), and reader
(client) reading it non-stop in infinite loop. Even without my own client i
see this problem in telent/nc - i.e. just ~4700 records coming and rest
somewhere "cached/queued".


--
View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Incomplete-writes-tp6336632p6338693.html
Sent from the Netty User Group mailing list archive at Nabble.com.