You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@mina.apache.org by "Alan D. Cabrera" <li...@toolazydogs.com> on 2011/08/05 16:35:12 UTC
Re: How to write a Compression Filter ?
On Jul 27, 2011, at 6:51 AM, Chris S wrote:
> Any hint, how to solve this puzzle, or what i am doing wrong ?
> I hope Mina 3.0 gets more simplified, there are to many ways to to the same
> thing. We have IOFilter, Protocol de/encoder etc. its quite confusing, what
> to use when.
I feel your pain. There's way too many classes in Mina and I am working very hard to delete as many as I can. I have my own sketch in the sandbox in adc. If you don't mind I'll use your compression filter as an example and hopefully it will look a bit cleaner that what mina 2.0 makes you do.
With that said I recommend extensive logging. Always pepper network code with logging from the start, you never know when you'll need it.
Regards,
Alan
Re: How to write a Compression Filter ?
Posted by Chris S <ch...@googlemail.com>.
Hi Alan,
feel free to use the compression filter as example ! Do you want to use it
as Mina 2.0 or Mina 3.0 exampe and were can i find it ?
I also tried to implement the compressor with a ProtocolDecoder and Encoder
but it seems that Mina 2.0 does not work with more than one
ProtocolCodecFilter. My Encoder and Decoder was ignored for some reason.
Thanks
Chris
On Fri, Aug 5, 2011 at 4:35 PM, Alan D. Cabrera <li...@toolazydogs.com>wrote:
>
> On Jul 27, 2011, at 6:51 AM, Chris S wrote:
>
> > Any hint, how to solve this puzzle, or what i am doing wrong ?
> > I hope Mina 3.0 gets more simplified, there are to many ways to to the
> same
> > thing. We have IOFilter, Protocol de/encoder etc. its quite confusing,
> what
> > to use when.
>
> I feel your pain. There's way too many classes in Mina and I am working
> very hard to delete as many as I can. I have my own sketch in the sandbox
> in adc. If you don't mind I'll use your compression filter as an example
> and hopefully it will look a bit cleaner that what mina 2.0 makes you do.
>
> With that said I recommend extensive logging. Always pepper network code
> with logging from the start, you never know when you'll need it.
>
>
> Regards,
> Alan
>
>