The websocket protocol specification is approaching final and the Jetty implementation and API have been tracking the draft and is ready when the spec and browsers are available. More over, Jetty release 7.5.0 now includes a capable websocket java
I have done some very rough preliminary benchmarks on the latest cometd-2.4.0-SNAPSHOT with the latest Jetty-7.5.0-SNAPSHOT and the results are rather impressive. The features that these two releases have added are: Optimised Jetty NIO with latest JVMs and JITs considered.
Since the very beginning, Jetty has been IOC friendly and thus has been able to be configured with spring. But the injecting and assembling the jetty container is not the only need that Jetty has for configuration and there are
Benchmarks like statistics can be incredibly misleading in ways that are only obvious with detailed analysis. Recently the apache HTTPCore project released some benchmark results whose headline results read as: Jetty HttpCore Linux BIO 35,342 56,185 Linux NIO 1,873 25,970
Now that the 2.4 servlet spec is final, I believe the time is right to start considering the end of life for the API. This may sound a little strange coming from somebody on the JSR and who has spent