Hi Rodrigo,
On 3/21/07, Rodrigo Madera <[EMAIL PROTECTED]> wrote:
I was studying the example code for MINA 1.0.2 and I came upon an
interesting fact: you provide two versions of the HTTP server. One that is
streaming and the other uses a codec to use high-level messages.
Can you please tell me which is "better"? What trade-offs can we expect with
message-based ones? (called codec-based in MINA lingo, right?)
Please always prefer codec-based one. I/O stream support is just for
legacy implementations, and won't scale enough.
Also, I can't resist asking here again since it's on the topic: is the way
all this is done going to change on MINA 2.0?
If so I better rush to get the gory details straight.
Most essential interfaces that you might have concern on won't change.
For example, your IoHandler and protocol codec implementations won't
need any changes other than very subtle cosmetic changes. However,
bootstrapping code will change quite a lot (i.e. IoAcceptor and
IoConnector), but it will be very small part of your implementation.
HTH,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6
