はてなブックマーク

A recent set of HTML5 discussions are changing the course of Comet. First, a recap of the last two years of Comet: With long-polling we set the bar to cross-browser push. With XHR streaming and ActiveXObject(’htmlfile’) we raised it to cross-browser streaming. With SSE we’ve been trying to raise the bar to native, cross-browser streaming. And there we’ve sat, hoping that browser vendors actually i

Introduction Comet is a giant hack. Even when it works flawlessly and efficiently, bringing us real-time interactive applications, deftly weaving around firewalls and browsers, avoiding unfriendly side effects, and cutting latency to near zero, it does so using mechanisms unforeseen by browser vendors, and unspecified by web standards. A few years ago, before it was widely used, or had been named,

Applications of Comet can be roughly categorized into event- and REST-based messaging. The characteristics of a Comet application define which Comet model is used, and different technological approaches can be used to maximize performance and scalability based upon the form of Comet. Event-based Comet In event-based Comet, messages are sent between agents with no assumptions about the meaning of t