Block messageReceived() until certain condition

[ljohnston]

I don't think Netty is reading from the channel. Without digging into the
code I'd suggest that Netty has read the pipelined requests in a single read
operation. Netty is probably processing as much of the read buffer (ie all
the pipelined requests) that it can before going back to the channel and
"not reading from it".

Is it really necessary to not read further requests from the channel into
memory before you've processed the first request? Is it not enough to ensure
they are processed in first in first out order? Can you explain a bit more
about your architecture?

Cheers
Lee




--
View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Block-messageReceived-until-certain-condition-tp5995452p6754316.html
Sent from the Netty User Group mailing list archive at Nabble.com.