<?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 access now, and support for the future</title>
	<atom:link href="http://ajaxian.com/archives/cross-domain-access-now-and-support-for-the-future/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/cross-domain-access-now-and-support-for-the-future</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: shadedecho</title>
		<link>http://ajaxian.com/archives/cross-domain-access-now-and-support-for-the-future/comment-page-1#comment-266364</link>
		<dc:creator>shadedecho</dc:creator>
		<pubDate>Mon, 04 Aug 2008 01:26:09 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3991#comment-266364</guid>
		<description>@V1-flXHR is better (IMHO) because it implements the native XHR API.  http://flxhr.flensed.com/   :)  

@ragjunk-You&#039;re right, the server has to grant permission. But that&#039;s specifically the reason, the point. Technologies which permit or encourage totally unrestricted x-domain access are far less secure.  And, with window.name, as kriszyp says, the server *does* have to opt-in, so it&#039;s a good thing.

But, more importantly for the open web revolution, for sites which want to publish their content to anyone, and it&#039;s safe for them to do so, they can use a &quot;*&quot; policy in their crossdomain.xml, which allows anyone to access it, without worrying about needing to specifically grant permission to each domain.</description>
		<content:encoded><![CDATA[<p>@V1-flXHR is better (IMHO) because it implements the native XHR API.  <a href="http://flxhr.flensed.com/" rel="nofollow">http://flxhr.flensed.com/</a>   :)  </p>
<p>@ragjunk-You&#8217;re right, the server has to grant permission. But that&#8217;s specifically the reason, the point. Technologies which permit or encourage totally unrestricted x-domain access are far less secure.  And, with window.name, as kriszyp says, the server *does* have to opt-in, so it&#8217;s a good thing.</p>
<p>But, more importantly for the open web revolution, for sites which want to publish their content to anyone, and it&#8217;s safe for them to do so, they can use a &#8220;*&#8221; policy in their crossdomain.xml, which allows anyone to access it, without worrying about needing to specifically grant permission to each domain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kriszyp</title>
		<link>http://ajaxian.com/archives/cross-domain-access-now-and-support-for-the-future/comment-page-1#comment-266361</link>
		<dc:creator>kriszyp</dc:creator>
		<pubDate>Sun, 03 Aug 2008 19:26:44 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3991#comment-266361</guid>
		<description>@ragjunk, @Loganathan: This approach requires that the target site opt-in by providing data using window.name technique, it doesn&#039;t enable you to break the &quot;steal&quot; data without the target site&#039;s consent; the target site must provide the data by setting the window.name. If you want the target  site to provide you data using the secure window.name technique, encourage them to implement the protocol (it is defined here: &lt;a href=&quot;http://www.sitepen.com/blog/2008/07/22/windowname-transport/&quot; rel=&quot;nofollow&quot;&gt;http://www.sitepen.com/blog/2008/07/22/windowname-transport/&lt;/a&gt;)</description>
		<content:encoded><![CDATA[<p>@ragjunk, @Loganathan: This approach requires that the target site opt-in by providing data using window.name technique, it doesn&#8217;t enable you to break the &#8220;steal&#8221; data without the target site&#8217;s consent; the target site must provide the data by setting the window.name. If you want the target  site to provide you data using the secure window.name technique, encourage them to implement the protocol (it is defined here: <a href="http://www.sitepen.com/blog/2008/07/22/windowname-transport/" rel="nofollow">http://www.sitepen.com/blog/2008/07/22/windowname-transport/</a>)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Loganathan</title>
		<link>http://ajaxian.com/archives/cross-domain-access-now-and-support-for-the-future/comment-page-1#comment-266353</link>
		<dc:creator>Loganathan</dc:creator>
		<pubDate>Sat, 02 Aug 2008 08:34:38 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3991#comment-266353</guid>
		<description>i am looking for  a solution to read some contents of another domain&#039;s page data .. i am loading into iframe in my page.. is it possible toaccess it.</description>
		<content:encoded><![CDATA[<p>i am looking for  a solution to read some contents of another domain&#8217;s page data .. i am loading into iframe in my page.. is it possible toaccess it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Loganathan</title>
		<link>http://ajaxian.com/archives/cross-domain-access-now-and-support-for-the-future/comment-page-1#comment-266352</link>
		<dc:creator>Loganathan</dc:creator>
		<pubDate>Sat, 02 Aug 2008 08:20:01 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3991#comment-266352</guid>
		<description>Will this help to fetch another domain&#039;s data through ? please tell me the answer?</description>
		<content:encoded><![CDATA[<p>Will this help to fetch another domain&#8217;s data through ? please tell me the answer?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: linb</title>
		<link>http://ajaxian.com/archives/cross-domain-access-now-and-support-for-the-future/comment-page-1#comment-266349</link>
		<dc:creator>linb</dc:creator>
		<pubDate>Sat, 02 Aug 2008 00:01:51 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3991#comment-266349</guid>
		<description>window.name technique is better for FIM. It enable you run an remote Ajax RIA application from a single local disk html file. 

&lt;a href=&quot;http://knol.google.com/k/yb-li/how-to-run-an-remote-ajax-ria&quot; rel=&quot;nofollow&quot;&gt;How to run an remote Ajax RIA application from a single local disk html file&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>window.name technique is better for FIM. It enable you run an remote Ajax RIA application from a single local disk html file. </p>
<p><a href="http://knol.google.com/k/yb-li/how-to-run-an-remote-ajax-ria" rel="nofollow">How to run an remote Ajax RIA application from a single local disk html file</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ragjunk</title>
		<link>http://ajaxian.com/archives/cross-domain-access-now-and-support-for-the-future/comment-page-1#comment-266346</link>
		<dc:creator>ragjunk</dc:creator>
		<pubDate>Fri, 01 Aug 2008 21:57:47 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3991#comment-266346</guid>
		<description>@V1: How would flash based XHR work, if my site is not in the crossdomain.xml of the target site? I want to do an XHR from my online app to any third party site, but I cannot do that because my site is not listed in any of their xdomain XML. So, I think, Kris&#039; work would help me better than using any of the flash based XHR, unless I missed something totally. (which happens many a times)</description>
		<content:encoded><![CDATA[<p>@V1: How would flash based XHR work, if my site is not in the crossdomain.xml of the target site? I want to do an XHR from my online app to any third party site, but I cannot do that because my site is not listed in any of their xdomain XML. So, I think, Kris&#8217; work would help me better than using any of the flash based XHR, unless I missed something totally. (which happens many a times)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kriszyp</title>
		<link>http://ajaxian.com/archives/cross-domain-access-now-and-support-for-the-future/comment-page-1#comment-266342</link>
		<dc:creator>kriszyp</dc:creator>
		<pubDate>Fri, 01 Aug 2008 19:42:34 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3991#comment-266342</guid>
		<description>Dojo does have an iframe mechanism for cross-domain loading that uses fragment identifiers (#hash) to transfer data. However, this technique is very limited, it can only send messages in 2K chunks. The windowName module and the new native APIs are much more efficient.</description>
		<content:encoded><![CDATA[<p>Dojo does have an iframe mechanism for cross-domain loading that uses fragment identifiers (#hash) to transfer data. However, this technique is very limited, it can only send messages in 2K chunks. The windowName module and the new native APIs are much more efficient.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nosredna</title>
		<link>http://ajaxian.com/archives/cross-domain-access-now-and-support-for-the-future/comment-page-1#comment-266335</link>
		<dc:creator>Nosredna</dc:creator>
		<pubDate>Fri, 01 Aug 2008 16:40:33 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3991#comment-266335</guid>
		<description>I&#039;m learning Dojo now, and it normally uses iFrames for this, right? Is there a case when using iFrames doesn&#039;t work?</description>
		<content:encoded><![CDATA[<p>I&#8217;m learning Dojo now, and it normally uses iFrames for this, right? Is there a case when using iFrames doesn&#8217;t work?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: V1</title>
		<link>http://ajaxian.com/archives/cross-domain-access-now-and-support-for-the-future/comment-page-1#comment-266326</link>
		<dc:creator>V1</dc:creator>
		<pubDate>Fri, 01 Aug 2008 13:20:13 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3991#comment-266326</guid>
		<description>ill rather use flashxhr, same effect less mess.</description>
		<content:encoded><![CDATA[<p>ill rather use flashxhr, same effect less mess.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: henrah</title>
		<link>http://ajaxian.com/archives/cross-domain-access-now-and-support-for-the-future/comment-page-1#comment-266324</link>
		<dc:creator>henrah</dc:creator>
		<pubDate>Fri, 01 Aug 2008 12:30:59 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3991#comment-266324</guid>
		<description>I don&#039;t think there are any browsers that can&#039;t do window.name message-passing; the proxy option is for supporting other sites which don&#039;t have a cross-domain request api to call.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think there are any browsers that can&#8217;t do window.name message-passing; the proxy option is for supporting other sites which don&#8217;t have a cross-domain request api to call.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

