1) I see in the FAQ it says:
When should I implement my protocol handler using filters? IoFilter is usually considered reusable just like we think about Servlet filters. Please implement commonly used business logic such as authorization and logging as a filter. In case you implement just complex multi-layer protocols like Kerberos, you could consider using org.apache.mina.handler.chain package. ------------ Authentication in my app will require a database lookup, and once the IoSession is authorized, I won't need to do that anymore. So to implement this as a filter, would I insert an ExecutorFilter before the Authentication filter to make sure the database work is offloaded to another thread? What about future messages after authentication, they will still be routed through these filters, and through the thread too, it seems like it would add latency. I already have an executor filter in place to take care of my IOHandler. Also, just out of curiosity, for my main IOHandler if I were to use ChainedIoHandlers instead of IoHandlers, would I add an ExecutorFilter before each one to give each their own thread pool? thanks in advance. I'm new to MINA and this list. --brigham
