"adrian(a)jboss.org" wrote : In fact, my real opinion is that you should do the reverse and provide | an implementation of an interface like the following: | | void run(InputStream is, OutputStream os) throws IOException {} | Except this makes it totally impossible to use NIO. Probably better would be to depend on an NIO framework (like Grizzly or MINA perhaps?) which could still conceptually allow you to fiddle with the socket and protocol details within the container, but at the same time support nice NIO things like reducing copying and better (than thread-per-connection/thread-per-request) threading models. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065923#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...