This greatly helps, Emmanuel, thank you, > There is one guarantee : once a session is associated with one IoProcessor > instance, it will be attached to the associatd thread. So if you don't add > an executor in your chain, then it's supposed to be thread-safe. However, if > you have cross-sessions elements, it's up to you to protect them against > concurrent access. However, if I have SINGLE IoHandlerAdapter for both NioAcceptors, thus my "number" variable is NOT thread safe? acceptor.setHandler(handler); NioSocketAcceptor acceptor = new NioSocketAcceptor(2); +code before
And if NioAcceptors run in several threads why do one needs an ExecutorFilter? I also studied MinaFtpServer source code. Suppose 100 clients requested 100 large files. If the ftp server has 100 threads it will not accept connections before at least one file will be transferred. The question is does MinaFtpServer not really scalable to transferring large files? What technique I must exploit to send large files by portions? Implement my own protocol? It would be great if messageReceived had a return type different from void to indicate operation was not completed and must be rescheduled later. -- Kind regards, Antonio Rodriges
