Hi Mike, Thanks a lot for your suggestion!
I'll definitely try the TextLineDecoder/TexlineEncoder. And, since there are other pre-implemented ProtocolDecoder/ProtocolEncoder like ObjectSerializationDecoder/ObjectSerializationEncoder, I assume that ProtocolEncoder/ProtocolDecoder will be the first thing to try. Thanks again, Jian On 10/29/06, Mike Grundvig <[EMAIL PROTECTED]> wrote:
I don't know of any recommendations specifically, but I do know that you can probably use the TextLine encoder/decoder to implement the first layer of your protocol. This has seemed to work with any delimiter-based protocol I've tried. Michael Grundvig Electrotank, Inc http://www.electrotank.com ----- Original Message ----- From: "jian wu" <[EMAIL PROTECTED]> To: <mina-dev@directory.apache.org> Sent: Saturday, October 28, 2006 12:16 PM Subject: ProtocolEncoder/Decoder v.s. MessageEncoder/Decoder > Hi, > > Mina provides two types of classes for encoding/decoding protocol data: > ProtocolEncoder/ProtocolDecoder, and MessageEncoder/MessageDecoder. > > Is there any guideline or recommendation when to use them? > > In my perticular use case, I'm looking into decoding and encoding a > protocol data with fixed start delimiter and end delimiter but length > could be varied due to internal data structure. > > Any suggestion would be really appreciated. > > Thanks, > > Jian >
