Structured message reading problem in Netty.

[Frederic Bregier]

Hi again,
While I was writing this post, there were new posts.
Just to try to help you about ChannelPipelineCoverage:

ChannelPipelineCoverage are just hit right now and are ignored by Netty.
So whatever the value you set (for the moment for the current version of
Netty),
nothing will change. However, they do have a meaning, even if nothing is
done
with it right now:
- ChannelPipelineCoverage("all") means that this kind of handler can be
  shared among all channel without any problem. The handler is a stateless
  handler (like StringDecoder).
- ChannelPipelineCoverage("one") is the opposite, that is to say the handler
  must be not shared among all channels since it is a statefull handler
  (like ObjectDecoder, FrameDecoder, and your decoder).

Right now your exceptions or malfunctions are probably due to concurrent
access on the server side to what should be private to one channel only.

HTH,
Frederic


-----
Hardware/Software Architect
-- 
View this message in context: http://n2.nabble.com/Structured-message-reading-problem-in-Netty.-tp2682454p2683235.html
Sent from the Netty User Group mailing list archive at Nabble.com.