Comet Resurrects "Push"

If Web-based applications are to have a true shot at displacing apps run off local hard disk drives, response time issues must be solved. As is typical for Web apps, though, new tools may help solve that problem. Comet (or Reverse AJAX), for example, is a significant departure from the “click-and-wait” interaction we traditionally associate with Web applications.

In fact, as with so many innovations--recall "push" technology or "application service providers"--timing is everything. Some applications that simply were too cumbersome 10 years ago now are possible with the spread of broadband, faster broadband, caching, peer-to-peer and software such as Comet.

Being right often is less "good" than being timely.

Comet is said by its supporters to resurrect push capabilities with better IP communications.

Simply put, push communications like Comet remove the requirement for an end user to explicitly click on a link or button to request information from a server.

Instead, the server is free to send messages to clients anytime a server-side event occurs. Therefore, content no longer needs the tried and true “click” to reach you. Web pages from hereon out will simply update as new data is made available, finally laying to rest the refresh button on your browser.

That has implications for bandwidth usage profiles, bandwidth intensity and usefulness of interactive or social applications.

Comet makes it possible to build any application that requires real-time updates, enabling true desktop-like functionality to be delivered over the Internet. That has implications for the effectiveness of chat applications, social networking, online games; news updates and online collaboration, for example.