<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Twitter is testing AJAX updates</title>
	<atom:link href="http://alikuru.com/twitter-is-testing-ajax-updates/feed/" rel="self" type="application/rss+xml" />
	<link>http://alikuru.com/twitter-is-testing-ajax-updates/</link>
	<description>Personal Weblog</description>
	<lastBuildDate>Mon, 08 Mar 2010 22:18:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ginx early review: Promising! &#171; Ali Kuru</title>
		<link>http://alikuru.com/twitter-is-testing-ajax-updates/comment-page-1/#comment-2</link>
		<dc:creator>Ginx early review: Promising! &#171; Ali Kuru</dc:creator>
		<pubDate>Sat, 14 Feb 2009 19:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://alikuru.com/?p=41#comment-2</guid>
		<description>[...] Manual updates of user timeline.You need to update your timeline by clicking “Sync now” link on the sidebar. I’m guessing that this method is chosen for limiting unnecessary API requests, but I also feel that it has to be changed. Twitter is all about live web and, I think, an AJAX’ified front-end, which checks updates in a given interval, would better serve its users (even Twitter is thinking about AJAX). [...]</description>
		<content:encoded><![CDATA[<p>[...] Manual updates of user timeline.You need to update your timeline by clicking “Sync now” link on the sidebar. I’m guessing that this method is chosen for limiting unnecessary API requests, but I also feel that it has to be changed. Twitter is all about live web and, I think, an AJAX’ified front-end, which checks updates in a given interval, would better serve its users (even Twitter is thinking about AJAX). [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
