Expanding Cross-Site Comet Options
by Kris ZypSeptember 9th, 2008An important feature of any comprehensive Comet framework is cross-site support. Cross-site capabilities can be particularly beneficial to Comet applications for a couple of reasons.
An important feature of any comprehensive Comet framework is cross-site support. Cross-site capabilities can be particularly beneficial to Comet applications for a couple of reasons.
HTTP Channels is the proposed Comet protocol for leveraging the semantics of HTTP REST for subscribing to resources and receiving resource/data modification notifications and closely integrates with HTTP.
Performance of a rich internet application (RIA) can manifest itself in a number of ways, such as responsiveness of user interaction and speed of rendering. This article is a follow-up to Performance of Grids for Streaming Data and covers Firefox 3.
ItsNat is a new Java web framework with Comet capabilities. In this article we’re going to see how ItsNat fits in the ecosystem of Comet technologies, and how ItsNat works and provides support for Comet.
In Orbited, we sometimes send multiple events in a single payload, particularly with the long-polling and polling transports. After we parse the data of each event, we call some event handler that a user has attached to the Orbited connection.

This time, we’ve asked our contributors the following: “With the recent addition of WebSocket to the HTML 5 recommendation, what impact will this have on your Comet implementation in both the short and long term? Do you see your approach to your preferred protocol changing as a result? What is your general impression of WebSocket?”
This is the third article in a series aimed at illustrating how to develop Lightstreamer v.3.x Adapters based on various technologies.
HTTP Channels is implemented in Dojo 1.2 with the HttpChannels module. HTTP Channels is intended to provide data synchronization and update notifications by leveraging the ubiquitous HTTP REST semantics.
At the Open Anzo project, we’re using Cometd Bayeux to expose JMS, the Java Message Service, to the browser.
A recent set of HTML5 discussions are changing the course of Comet. The HTML5 specification now offers WebSocket, a full-duplex communications channel that operates over a single socket.
UniversalComet is a proof of concept Comet implementation using the Google App Engine.
Read moreMatt Raible recently posted the results of this research on Dojo support in Java frameworks
Read moreMost mobile web browsers on today's smart phones support both Ajax and Comet. Are there useful statistics of usage data?
Read moreJoe Walker and Nikolai Onken are speaking at Devoxx this week on the topic of Creating amazing user interfaces with Dojo and DWR
Read more


