<?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: Cross Domain XHR W3C proposal</title>
	<atom:link href="http://ajaxian.com/archives/cross-domain-xhr-w3c-proposal/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/cross-domain-xhr-w3c-proposal</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 09 Feb 2012 06:55:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: backdraft</title>
		<link>http://ajaxian.com/archives/cross-domain-xhr-w3c-proposal/comment-page-1#comment-259253</link>
		<dc:creator>backdraft</dc:creator>
		<pubDate>Fri, 23 Nov 2007 13:02:06 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3027#comment-259253</guid>
		<description>very nice implementation. hope this will come soon!</description>
		<content:encoded><![CDATA[<p>very nice implementation. hope this will come soon!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tiago Albineli Motta</title>
		<link>http://ajaxian.com/archives/cross-domain-xhr-w3c-proposal/comment-page-1#comment-259221</link>
		<dc:creator>Tiago Albineli Motta</dc:creator>
		<pubDate>Thu, 22 Nov 2007 19:33:33 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3027#comment-259221</guid>
		<description>While it&#039;s not possible we have to use script on-demand. Globo Videos started using this approach in the new version.</description>
		<content:encoded><![CDATA[<p>While it&#8217;s not possible we have to use script on-demand. Globo Videos started using this approach in the new version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barnaby Claydon</title>
		<link>http://ajaxian.com/archives/cross-domain-xhr-w3c-proposal/comment-page-1#comment-259190</link>
		<dc:creator>Barnaby Claydon</dc:creator>
		<pubDate>Thu, 22 Nov 2007 01:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3027#comment-259190</guid>
		<description>Interesting proposal. I hope it gets adopted although there&#039;s certainly a need for something even more comprehensive.

Out of curiousity, where it states &quot;...forces developers to use &lt;strong&gt;more secure explicit forms of authentication maintanence&lt;/strong&gt;.&quot; what exactly would those be? I&#039;m in need of auth maintenance on a current project in this XHR context and am intrigued by what this statement implies.</description>
		<content:encoded><![CDATA[<p>Interesting proposal. I hope it gets adopted although there&#8217;s certainly a need for something even more comprehensive.</p>
<p>Out of curiousity, where it states &#8220;&#8230;forces developers to use <strong>more secure explicit forms of authentication maintanence</strong>.&#8221; what exactly would those be? I&#8217;m in need of auth maintenance on a current project in this XHR context and am intrigued by what this statement implies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Levine</title>
		<link>http://ajaxian.com/archives/cross-domain-xhr-w3c-proposal/comment-page-1#comment-259174</link>
		<dc:creator>Jason Levine</dc:creator>
		<pubDate>Wed, 21 Nov 2007 21:11:48 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3027#comment-259174</guid>
		<description>Very nice.  At the very least, it would remove an annoyance I have with my scripts.  If I have a.domain.com and b.domain.com, JavaScript sees them as separate domains and refuses to allow XMLHTTP connections between the two.  With this, I could set up each to get connections from the other and finally be able to communicate between all of my *.domain.com websites!</description>
		<content:encoded><![CDATA[<p>Very nice.  At the very least, it would remove an annoyance I have with my scripts.  If I have a.domain.com and b.domain.com, JavaScript sees them as separate domains and refuses to allow XMLHTTP connections between the two.  With this, I could set up each to get connections from the other and finally be able to communicate between all of my *.domain.com websites!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Holton</title>
		<link>http://ajaxian.com/archives/cross-domain-xhr-w3c-proposal/comment-page-1#comment-259172</link>
		<dc:creator>Mark Holton</dc:creator>
		<pubDate>Wed, 21 Nov 2007 20:43:07 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3027#comment-259172</guid>
		<description>...interesting... the more news, feedback, thoughts on this, the better.</description>
		<content:encoded><![CDATA[<p>&#8230;interesting&#8230; the more news, feedback, thoughts on this, the better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Travaglini</title>
		<link>http://ajaxian.com/archives/cross-domain-xhr-w3c-proposal/comment-page-1#comment-259147</link>
		<dc:creator>Joe Travaglini</dc:creator>
		<pubDate>Wed, 21 Nov 2007 15:30:22 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3027#comment-259147</guid>
		<description>This is great news!  It will remove the necessity of my numerous poor-man&#039;s-proxy scripts to broker my AJAX requests...

But what will be the migration strategy for the various web and app servers to adopt it?</description>
		<content:encoded><![CDATA[<p>This is great news!  It will remove the necessity of my numerous poor-man&#8217;s-proxy scripts to broker my AJAX requests&#8230;</p>
<p>But what will be the migration strategy for the various web and app servers to adopt it?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

