« When the story doesn’t fit | Main | Ruby on Rails moves to 1.1 »

March 30, 2006

Catching the tail of COMET

From the Irish Developer Network I found this very thorough description of AJAX's next phase--COMET.

The article goes into detail (not too much) on the architectural differences between AJAX and COMET.  The main benefit, and if you've tried any of the online apps below you've seen it yourself (I like the GMail-GTalk integration myself), is that COMET is more persistent with long-term connections.  Activities that take time to complete.

So the question is, should more apps be moved online via AJAX or COMET?  I'm not so sure.  I still live in an online-offline world, so I need applications that run when I'm not connected.  That being said, I see a lot of potential for internal applications like expense reports or maybe even group spreadsheets and word processors.  Even an internal IM system might be a good application.

What do you think are the AJAX or COMET apps that have the most potential?

Tags: , , ,

Posted by Tris Hussey on March 30, 2006 | Permalink

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/t/trackback/384091/4561925

Listed below are links to weblogs that reference Catching the tail of COMET:

Comments

You may be interested in a sample online/offline AJAX demo that I put together. It's a wiki that can be loaded when disconnected, relying on the browser cache and Flash persistent storage.

Check it out: http://blog.monstuff.com/archives/000272.html

Support for disconnected operations in web application is possible, but it's still a lot of work and requires some browser extensions.

Posted by: Julien Couvreur | Apr 3, 2006 1:29:22 PM

Post a comment