Articles

Recent discussions on Comet server performance have focused on sockets and IO. However, different usage profiles can cause some very different performance results.

Are threads really that bad? Is there a significant difference between IO and NIO for Java-based Comet servers? The assumptions, conclusions, and contradictory evidence might surprise you.

REST Channels is a Comet protocol for data notifications designed to integrate with a REST architecture. REST Channels leverages the semantics of HTTP messaging and provides notifications of the creation, update, and deletion of resources using REST’s resource identifiers (URI) in order to provide real-time views of data from web clients.

Chat rooms have been cited as the “Hello World” application of Ajax Comet because chat is something that everybody can understand and represents a good exemplar of the technology. With my own work, I have frequently used the cometD chat demo as the basis of benchmarking and scalability tests.

One of the common misconceptions regarding cometD, is that it can only do publish-subscribe messaging. While this misconception may be encouraged by the protocol design, it is definitely possible to do private messaging with cometD

This tutorial will show you how to build a simple broadcast application for numerical data and represent that data graphically in the browser. The resulting user interface is very simplistic so that we can focus on the important parts of real-time applications.

Recently I integrated Jetty’s cometD implementation of Bayeux with Persevere. With this new functionality, Bayeux-based Comet communication can be used to route messages through Persevere’s stored objects.

Stomp is an incredibly straightforward message queue protocol. Stomp derives its name from an acronym with the same letters that stand for Streaming Text-Oriented Messaging Protocol.

In this article we are going to introduce the two different development approaches for Comet, client-centric and server-centric, and how ItsNat, in spite of its server-centric nature, is familiar for any JavaScript developer.

I constantly get people saying “Comet, pftt… Flash already has a socket.” I agree with the basic sentiment; I’d rather have a socket than Comet, but I’ve always been uneasy about depending on Flash