<?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: Quick Widget Update</title>
	<atom:link href="http://www.cycloneranger.com/2007/01/quick-widget-update.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.cycloneranger.com/2007/01/quick-widget-update.html</link>
	<description>&#34;I see patterns&#34; - Ernie Hacks</description>
	<lastBuildDate>Mon, 22 Mar 2010 20:05:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Justin</title>
		<link>http://www.cycloneranger.com/2007/01/quick-widget-update.html/comment-page-1#comment-31</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-31</guid>
		<description>I&#039;m not sure I really understand what a widget is I don&#039;t think.  Isn&#039;t it just a piece of display code that draws from a source other than the requested server?  I can&#039;t really figure how your assertions fit into this model.  Basically the &#039;page&#039; is still just a jumble of HTML rendered by the browser.  Ajax allows for some dynamism in the display by introducing a pseudo client-server model, but the website remains stateless in a purely technical sense, right?  What am I missing here?

I have to admit when I hear &quot;widget&quot; I feel the same bile rising as when I hear marketing buzzword.  To me it doesn&#039;t seem like anything revolutionary at all is happening.  Again, what am I missing?</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure I really understand what a widget is I don&#8217;t think.  Isn&#8217;t it just a piece of display code that draws from a source other than the requested server?  I can&#8217;t really figure how your assertions fit into this model.  Basically the &#8216;page&#8217; is still just a jumble of HTML rendered by the browser.  Ajax allows for some dynamism in the display by introducing a pseudo client-server model, but the website remains stateless in a purely technical sense, right?  What am I missing here?</p>
<p>I have to admit when I hear &#8220;widget&#8221; I feel the same bile rising as when I hear marketing buzzword.  To me it doesn&#8217;t seem like anything revolutionary at all is happening.  Again, what am I missing?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris</title>
		<link>http://www.cycloneranger.com/2007/01/quick-widget-update.html/comment-page-1#comment-32</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-32</guid>
		<description>Yes, a Widget is exactly a piece of display code that draws a source from another server - both content and application data.

One of the constraints of a website though is that it&#039;s functionality is restricted to a specific domain and context.  Widgets can function cross-domain - Google Adsense is a great example of this functionality, as is their Urchin tracker.  But the repeated implementations give Google cross-domain knowledge of user behaviors, and potentially cross-domain functionality.

The revolution is less the &quot;how&quot; and more the &quot;what&quot;.  As user agents begin to really support JavaScript and long-tail content creators go searching for free site functionality, Widgets increase in presence and power, opening the door for new products like MyBlogLog.</description>
		<content:encoded><![CDATA[<p>Yes, a Widget is exactly a piece of display code that draws a source from another server &#8211; both content and application data.</p>
<p>One of the constraints of a website though is that it&#8217;s functionality is restricted to a specific domain and context.  Widgets can function cross-domain &#8211; Google Adsense is a great example of this functionality, as is their Urchin tracker.  But the repeated implementations give Google cross-domain knowledge of user behaviors, and potentially cross-domain functionality.</p>
<p>The revolution is less the &#8220;how&#8221; and more the &#8220;what&#8221;.  As user agents begin to really support JavaScript and long-tail content creators go searching for free site functionality, Widgets increase in presence and power, opening the door for new products like MyBlogLog.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
