Articles

On December 22nd, the popular Spanish Christmas Lottery took place. This lottery is arranged by the Spanish Government and has a very long tradition in Spain, especially at Christmas when the rewards are the greatest.

When writing about Comet technologies, sometimes we tend to be a bit abstract and theoretical. In this case, I would like to focus on concrete working examples.

I recall just a few years ago hearing warning that Ajax should be avoided. As I recall, the biggest objection to Ajax at the time was that users were not ready for Ajax. Many felt that users expected pages to fully refresh and re-rendering part of a page would cause confusion.

What factors go into the decision of choosing between Ajax, Flash, and Silverlight for your Comet applications?

cometd-jetty now has an acknowledged message mechanism for reliable message delivery.

I recently had the chance to interview the creator of iStreamLight, an open-source library for the iPhone that implements the network protocol of Lightstreamer.

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.