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
The CometD project implements various Comet techniques to implement a web messaging bus. You can find an introduction to CometD here. Web applications often need to access resources residing on different servers, making the request to access those resources a
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) –
It all started when my colleague Joakim showed me the results of some JSON libraries benchmarks he was doing, which showed Jackson to be the clear winner among many libraries. So I decided that for the upcoming CometD 2.4.0 release
In the last blog entry I talked about message flow control using CometD‘s lazy channels. Now I want to show how it is possible to achieve a similar flow control using specialized listeners that allow to manipulate the ServerSession message
The Codemotion conference slides of my talk on Comet and WebSocket web applications are available here: slideshare, download.
In the CometD introduction post, I explained how the CometD project provides a solution for writing low-latency server-side event-driven web applications. Examples of this kind of applications are financial applications that provide stock quote price updates, or online games, or