title: Use Jetty or Netty?
body: <p>We're in the process of writing a high-performance server for processing messages. We've been using Jetty for several years and like it, but Netty looks like it has some cool features. In particular, it has support for asynchronous processing so a thread doesn't have to be tied up waiting for the system to process a given message. It's designed to solve the C10k problem.</p>
  
  <p>I know that Jetty has some support for NIO internally. Does it also have an asynchronous model?</p>
  
  <p>The messages are likely to be in http format. Does Netty have any performance advantages over Jetty when doing plain old http?</p>
  
  <p>I'd like to have all the convenient features of a real servlet container, but not at the cost of reduced performance. </p>