Articles

The latest release of the Persevere Server (0.9.5) now includes Comet support. The Persevere Server is a web accessible database and service side JavaScript server that exposes persistent data storage as RESTful HTTP/JSON web services.

There is a lot of confusion about guaranteed messaging. Many products claim some level of guaranteed or reliable messaging, but what does it really mean?

With the increasing interest in Comet and the recent Super Mario Brothers implementation and the Embedding and Encoding JavaScript analysis, I thought it would be interesting to take a look at games based on Comet techniques.

As I write this, we’re waiting for the results of London’s Mayoral election. The position of Mayor has only been around since 2000, and this year a too-close-to-call contest between two of the most colourful politicians in the country has kept the race on the front pages of the papers for weeks.

Comet Gazing is a semi-regular feature on Comet Daily. We pose a question to our Contributors and post the answers. This time, we’ve asked our contributors the question: “What do you find most frustrating about Comet development, and how do you workaround or deal with the issue?”

After publishing the article “Hello World” with Lightstreamer, I received many requests to release a version of that tutorial for .NET developers. Therefore, in this installment we will work on a .NET port of the Java Data Adapter that we illustrated in the previous article. In particular, both a C# version and a Visual Basic version will be shown.

Pub/sub is a popular architecture for Comet development. Simple applications may only need to deal with a single pub/sub broker, but more complex applications may involve multiple pub/sub brokers. Path prefixing and URL topics provide two means for integrating multiple pub/sub brokers.

Web applications using Comet (a.k.a. Ajax Push) are growing in popularity, but little has been said so far on the new problems that push operations might introduce. In this article, I would like to discuss one issue I’ve frequently seen over the last year, which is what I call Delayed Push Operations (DPO). I’ll also cover several ways to reduce the probability of creating data congestion.

I recently blogged about the relationship between REST and RPC. REST and RPC also have a relationship with the publish and subscribe architecture. Joe Walker recently discussed three major API styles for Comet: traditional, message-passing, and data synchronization. These API styles correlate to these three architectural styles, respectively: RPC, pub/sub, and REST.

Dave Crane says you usually don’t have to look far to find a place where Comet helps. He also talks about the rapid development of Comet, how he discovered Comet, and using Comet alongside a traditional domain model.