Yes, it's the first param. Is it replacing the getMessageTypes() callback
inside the Message encoder, or does it have another use?
G
Trustin Lee wrote:
>
> On 11/8/07, gorano <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> Sorry of being lazy and not figuring this out my self.
>>
>> (1)
>>
>> IoSession.getAttachment is now deprecated, do I use the getAttribute with
>> a
>> key instead?
>
> Yes. You could use AttributeKey as a key for the best performance.
>
>> (2)
>>
>> DemuxingProtocolCodecFactory.register(...) is gone. Guess I should use
>> addMessageDecoder and addMessageEncoder instead.
>>
>> addMessageDecoder takes 2 args though
>>
>> Inside my MessageEncoder I use stuff like:
>>
>> public Set<Class<IoBuffer>> getMessageTypes(){
>> return
>> Collections.<Class<IoBuffer>>singleton(IoBuffer.class);
>> }
>>
>> Is this second param replacing this in some way?
>
> Wasn't it the first param? For example...
>
> addMessageEncoder(String.class, StringMessageEncoder.class);
>
> HTH,
> Trustin
>
> --
> what we call human nature is actually human habit
> --
> http://gleamynode.net/
> --
> PGP Key ID: 0x0255ECA6
>
>
--
View this message in context:
http://www.nabble.com/Mina-2-snapshot-changes-tf4770428s16868.html#a13645635
Sent from the Apache MINA Support Forum mailing list archive at Nabble.com.
