I don't see what the your link has to do with the
DemuxingProtocolCodecFactory. AFAIK the Demuxer can be used to encode
and decode message according to certain message classes.
So it should be perfectly possible to register two different
MessageEncoders.
If not, then what is the point of the Demuxer?
Jeroen Brattinga
mat wrote:
http://www.nabble.com/Why-only-one-ProtocolCodecFilter-per-chain-tf3884603.html#a11012504
On 6/30/07, Messi Chan <[EMAIL PROTECTED]> wrote:
Hi, all
I have a doubt about DemuxingProtocolCodecFactory.
I register two MessageEncoders one for class A, and the other for
class B.
When my server try to encode A first time, it work fine. But when it try
to
encode B next time, I got the exception(unexpected message types ....B).
Is DemuxingProtocolCodecFactory just allowed register one
MessageEncoder?
I
want someone's confirmation.
thx a lot :D
--
View this message in context:
http://www.nabble.com/some-trouble-about-DemuxingProtocolCodecFactory-tf4005109.html#a11374435
Sent from the mina dev mailing list archive at Nabble.com.
