A couple of months ago the CometD Project released its third major version, CometD 3.0.0 (announcement). Since then I wanted to write a blog about this major release, but work on HTTP 2 kept me busy. Today CometD 3.0.1 was
The SPDY protocol will be the next web revolution. The HTTP-bis working group has been rechartered to use SPDY as the basis for HTTP 2.0, so network and server vendors are starting to update their offerings to include SPDY support.
Jetty has always been in the front line on the implementation of the WebSocket Protocol. The CometD project leverages the Jetty WebSocket implementation to its maximum, to achieve great scalability and minimal latencies. Until now, however, support for WebSocket over
Slightly more than one year has passed since the last CometD 2 benchmarks, and more than three years since the CometD 1 benchmark. During this year we have done a lot of work on CometD, both by adding features and
CometD 2.4.0.beta1 has been released. This is a major release that brings in a few new Java API (see this issue) – client-side channels can now be released to save memory, along with an API deprecation (see this issue) –
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.