<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Comet Is the New Ajax</title>
	<atom:link href="http://benramsey.com/archives/comet-is-the-new-ajax/feed/" rel="self" type="application/rss+xml" />
	<link>http://benramsey.com/archives/comet-is-the-new-ajax/</link>
	<description>PHP and Other Techno-babble</description>
	<pubDate>Sat, 22 Nov 2008 11:59:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: A Time to Laugh &#187; 2006 is the new 1984</title>
		<link>http://benramsey.com/archives/comet-is-the-new-ajax/#comment-5171</link>
		<dc:creator>A Time to Laugh &#187; 2006 is the new 1984</dc:creator>
		<pubDate>Fri, 29 Sep 2006 18:35:20 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=140#comment-5171</guid>
		<description>[...] Comet is the new Ajax. [...]</description>
		<content:encoded><![CDATA[<p>[...] Comet is the new Ajax. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tecM0</title>
		<link>http://benramsey.com/archives/comet-is-the-new-ajax/#comment-4035</link>
		<dc:creator>tecM0</dc:creator>
		<pubDate>Thu, 22 Jun 2006 22:25:04 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=140#comment-4035</guid>
		<description>Hooray! A new name for someting we call "http server push or something like that" since 2000. i agree with my previous speakers: scalability is'nt that easy AND you will be happy
to have the possibilities of XMLHttpRequest after running
against the first firewall and/or proxy. 
also some (old) browsers (mostly khtml driven like safari,konqueror,...) rendering
the page right after they have received ALL data. a endless
load gives you a nice blank screen...untill you or the server
killing the connection.

anyway...a nice field to play with and for some applications
a good approach to get a step closer to "realtime".

tecM0</description>
		<content:encoded><![CDATA[<p>Hooray! A new name for someting we call &#8220;http server push or something like that&#8221; since 2000. i agree with my previous speakers: scalability is&#8217;nt that easy AND you will be happy<br />
to have the possibilities of XMLHttpRequest after running<br />
against the first firewall and/or proxy. <br />
also some (old) browsers (mostly khtml driven like safari,konqueror,...) rendering<br />
the page right after they have received ALL data. a endless<br />
load gives you a nice blank screen&#8230;untill you or the server<br />
killing the connection.</p>
<p>anyway&#8230;a nice field to play with and for some applications<br />
a good approach to get a step closer to &#8220;realtime&#8221;.</p>
<p>tecM0</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CodeWord: Apokalyptik &#187; Blog Archive &#187; Note to self</title>
		<link>http://benramsey.com/archives/comet-is-the-new-ajax/#comment-3763</link>
		<dc:creator>CodeWord: Apokalyptik &#187; Blog Archive &#187; Note to self</dc:creator>
		<pubDate>Sat, 20 May 2006 23:34:08 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=140#comment-3763</guid>
		<description>[...] Just Consider this post a personal yellow sticky note on my web space  Read These: &#8220;Comet is the new Ajax&#8221;, and &#8220;Comet, Low Latency Data for the Browser&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] Just Consider this post a personal yellow sticky note on my web space  Read These: &#8220;Comet is the new Ajax&#8221;, and &#8220;Comet, Low Latency Data for the Browser&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Ramsey</title>
		<link>http://benramsey.com/archives/comet-is-the-new-ajax/#comment-3716</link>
		<dc:creator>Ben Ramsey</dc:creator>
		<pubDate>Thu, 18 May 2006 12:46:18 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=140#comment-3716</guid>
		<description>It's not just you. Adam Rifkin tells me:

bq. The mod-pubsub rewrite is something we're planning on open sourcing with a BSD license sometime in the next few months. 'Til then, the site is down.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not just you. Adam Rifkin tells me:</p>
<blockquote>
<p>The mod-pubsub rewrite is something we&#8217;re planning on open sourcing with a BSD license sometime in the next few months. &#8216;Til then, the site is down.</p>
</blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Mulder</title>
		<link>http://benramsey.com/archives/comet-is-the-new-ajax/#comment-3712</link>
		<dc:creator>Tom Mulder</dc:creator>
		<pubDate>Thu, 18 May 2006 08:02:17 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=140#comment-3712</guid>
		<description>Is it me or is the pubsub site unreachable ?</description>
		<content:encoded><![CDATA[<p>Is it me or is the pubsub site unreachable ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Eichorn</title>
		<link>http://benramsey.com/archives/comet-is-the-new-ajax/#comment-3557</link>
		<dc:creator>Joshua Eichorn</dc:creator>
		<pubDate>Thu, 04 May 2006 17:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=140#comment-3557</guid>
		<description>The biggest problem i see with comet is scalability.  Its no problem to throw servers at the problem if your google or a well funded startup with a few users.

Nothing like abusing HTTP to make all your current scaling techniques obsolete.</description>
		<content:encoded><![CDATA[<p>The biggest problem i see with comet is scalability.  Its no problem to throw servers at the problem if your google or a well funded startup with a few users.</p>
<p>Nothing like abusing HTTP to make all your current scaling techniques obsolete.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Ramsey</title>
		<link>http://benramsey.com/archives/comet-is-the-new-ajax/#comment-3543</link>
		<dc:creator>Ben Ramsey</dc:creator>
		<pubDate>Wed, 03 May 2006 21:32:13 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=140#comment-3543</guid>
		<description>True, but it has &lt;em&gt;everything&lt;/em&gt; to do with asynchronus HTTP transactions. I think many people are confusing AJAX as being a slick DHTML interface.</description>
		<content:encoded><![CDATA[<p>True, but it has <em>everything</em> to do with asynchronus HTTP transactions. I think many people are confusing AJAX as being a slick DHTML interface.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Wenz</title>
		<link>http://benramsey.com/archives/comet-is-the-new-ajax/#comment-3539</link>
		<dc:creator>Christian Wenz</dc:creator>
		<pubDate>Wed, 03 May 2006 20:34:27 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=140#comment-3539</guid>
		<description>just wanted to add that AJAX does not necessarily have _anything_ to do with XML :-)</description>
		<content:encoded><![CDATA[<p>just wanted to add that AJAX does not necessarily have <em>anything</em> to do with XML <img src='http://benramsey.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lazy Coder</title>
		<link>http://benramsey.com/archives/comet-is-the-new-ajax/#comment-3532</link>
		<dc:creator>Lazy Coder</dc:creator>
		<pubDate>Wed, 03 May 2006 09:44:16 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=140#comment-3532</guid>
		<description>&lt;strong&gt;Comet&lt;/strong&gt;

"
This time last year, a single word began a revolution in Web design. Coined and published on February...</description>
		<content:encoded><![CDATA[<p><strong>Comet</strong></p>
<p>&#8221;<br />
This time last year, a single word began a revolution in Web design. Coined and published on February&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rami Kayyali</title>
		<link>http://benramsey.com/archives/comet-is-the-new-ajax/#comment-3530</link>
		<dc:creator>Rami Kayyali</dc:creator>
		<pubDate>Wed, 03 May 2006 07:50:08 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=140#comment-3530</guid>
		<description>Remember when Comet used to be called HTTP Push? Yeah, the kind of thing that was used in making IRC-like web apps?

Comet isn't really new (just like Ajax wasn't). Granted, a cute name for an old technology does wonders (watch the Ajax craze). But as far as I remember, HTTP Push wasn't a viable option for high-traffic sites, it doesn't scale very well, especially not on cheap hardware.

The difference between Comet and HTTP Push is that the latter wasn't used for anything except data, now Comet's uses the same concept to do JavaScript.

I'd love to see how Comet will perform against Ajax.</description>
		<content:encoded><![CDATA[<p>Remember when Comet used to be called HTTP Push? Yeah, the kind of thing that was used in making IRC-like web apps?</p>
<p>Comet isn&#8217;t really new (just like Ajax wasn&#8217;t). Granted, a cute name for an old technology does wonders (watch the Ajax craze). But as far as I remember, HTTP Push wasn&#8217;t a viable option for high-traffic sites, it doesn&#8217;t scale very well, especially not on cheap hardware.</p>
<p>The difference between Comet and HTTP Push is that the latter wasn&#8217;t used for anything except data, now Comet&#8217;s uses the same concept to do JavaScript.</p>
<p>I&#8217;d love to see how Comet will perform against Ajax.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: boots</title>
		<link>http://benramsey.com/archives/comet-is-the-new-ajax/#comment-3527</link>
		<dc:creator>boots</dc:creator>
		<pubDate>Wed, 03 May 2006 02:07:18 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=140#comment-3527</guid>
		<description>Cool, but keeping open connections is rather expensive, not? Great for controlled intranet apps with lots of hardware (well -- it has worked for us for years). Otherwise, how do you scale this beast and deal with failover gracefully? OTOH, I'm glad to hear that there is some pre-built support for this in existing and supported toolkits -- makes future implementations that much more straight-forward.</description>
		<content:encoded><![CDATA[<p>Cool, but keeping open connections is rather expensive, not? Great for controlled intranet apps with lots of hardware (well&#8212;it has worked for us for years). Otherwise, how do you scale this beast and deal with failover gracefully? OTOH, I&#8217;m glad to hear that there is some pre-built support for this in existing and supported toolkits&#8212;makes future implementations that much more straight-forward.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Ramsey</title>
		<link>http://benramsey.com/archives/comet-is-the-new-ajax/#comment-3524</link>
		<dc:creator>Ben Ramsey</dc:creator>
		<pubDate>Tue, 02 May 2006 23:51:44 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=140#comment-3524</guid>
		<description>And AJAX has been around since 1998 with the XMLHTTP request object in Microsoft Internet Explorer. The combination of the tools (JavaScript and XML) didn't have a name until last year, and, guess what, when there was a name for it everyone could finally describe it with simple terms, technologist and lay person alike. Alex further explains the reasoning for the new name on his blog post. It's a good read:

http://alex.dojotoolkit.org/?p=545</description>
		<content:encoded><![CDATA[<p>And AJAX has been around since 1998 with the XMLHTTP request object in Microsoft Internet Explorer. The combination of the tools (JavaScript and XML) didn&#8217;t have a name until last year, and, guess what, when there was a name for it everyone could finally describe it with simple terms, technologist and lay person alike. Alex further explains the reasoning for the new name on his blog post. It&#8217;s a good read:</p>
<p><a href="http://alex.dojotoolkit.org/?p=545" rel="nofollow">http://alex.dojotoolkit.org/?p=545</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evert</title>
		<link>http://benramsey.com/archives/comet-is-the-new-ajax/#comment-3523</link>
		<dc:creator>Evert</dc:creator>
		<pubDate>Tue, 02 May 2006 23:47:22 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=140#comment-3523</guid>
		<description>but why do we need another fancy name? I have saw this in use since at least the year 2000</description>
		<content:encoded><![CDATA[<p>but why do we need another fancy name? I have saw this in use since at least the year 2000</p>
]]></content:encoded>
	</item>
</channel>
</rss>
