Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Jetty 6 is a fully featured web server for static and dynamic content. Unlike separate server/container solutions, this means that your web server and web application run in the same process, without interconnection overheads and complications. in addition, as a pure java component, Jetty 6 can be simply included in your application for demonstration, distribution or deployment. It is available on all Java supported platforms. Open Source Jetty 6 is developed under the guidance of Mort Bay Consulting.


Jetty 6 supports a new feature called Continuations that will allow scalable AJAX applications to be built, with threadless waiting for asynchronous events. As per scalability it is one of the major concerns of this product that would be supported by the advent of AJAX with the response to offer a feature called Continuations. Where in it allows a request to be suspended and resumed later in the process. In addition it is a java Filter or Servlet that is handling an AJAX request, may now request a Continuation object that can be used to effectively suspend the request and free the current thread. The request is resumed after a timeout or immediately if the resume method is called on the Continuation object. Jetty 6 employs a number of innovative strategies to ensure that only the resources that are actually required are assigned to a connection and only for the duration of they are needed. This careful resource management gives Jetty an architecture designed to scale to meet the needs of AJAX applications

The summary features of Jetty6:

  • Codebase completely rearchitected and slimlined
  • Continuations API for efficient AJAX polling
  • Improved dependency injection and inversion of control design of components
  • Improved interceptor design of handlers
  • Smart split buffer design for efficient asynchronous flushing and avoiding chunking.
  • Optional use of NIO Buffering so that efficient direct buffers and memory mapped files can be used.
  • Optional use of NIO non-blocking scheduling so that threads are not allocated per connection.
  • Optional use of NIO gather writes, so that for example a HTTP header and a memory mapped file may be sent as a single operation.
Contact the core Jetty developers at
private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery