<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Bloggitation comments on COMET - the next stage of AJAX</title>
    <link>http://typo.onxen.info/</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Bloggitation comments</description>
    <item>
      <title>"COMET - the next stage of AJAX" by stoyan</title>
      <description>&lt;p&gt;The &lt;a href="http://www.pushlets.com/"&gt;new player&lt;/a&gt; on the Web 2.0 scene? Ajax improved the UI, Comet seems more server-side oriented. Via a persistent &lt;span class="caps"&gt;HTTP&lt;/span&gt; connections it making the communication with the server &amp;#8220;push-based&amp;#8221; &amp;#8211; the server, asynchroniously pushing data to the client side, based on some events. Better than Ajax for community-driven applications.&lt;/p&gt;


	&lt;p&gt;Bad according to some ppl, it can be just an &lt;a href="http://ajaxpatterns.org/HTTP_Streaming"&gt;Ajax pattern &amp;#8211; &lt;span class="caps"&gt;HTTP &lt;/span&gt;Streaming&lt;/a&gt; . Still pretty &lt;a href="http://digg.com/programming/COMET_-_the_next_AJAX"&gt;long and informative discussion on Digg&lt;/a&gt; .&lt;/p&gt;

</description>
      <pubDate>Sun, 26 Mar 2006 18:54:00 PST</pubDate>
      <guid>&lt;a href="/articles/2006/03/26/comet-the-next-stage-of-ajax"&gt;COMET - the next stage of AJAX&lt;/a&gt;</guid>
      <link>&lt;a href="/articles/2006/03/26/comet-the-next-stage-of-ajax"&gt;COMET - the next stage of AJAX&lt;/a&gt;</link>
    </item>
  </channel>
</rss>
