<?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: Silverlight HTTP Networking Stack - Part 2 (Cross Domain Communication Overview)</title>
	<atom:link href="http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview/feed/" rel="self" type="application/rss+xml" />
	<link>http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview</link>
	<description></description>
	<pubDate>Mon, 08 Sep 2008 17:25:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Evgeniy</title>
		<link>http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview#comment-50756</link>
		<dc:creator>Evgeniy</dc:creator>
		<pubDate>Tue, 02 Sep 2008 10:51:11 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview/#comment-50756</guid>
		<description>Thanks a lot for the review. 
Do you plan to change the restriction on the cross domain Uri?
Now it seems to be no sense in making remote calls to Sharepoint lists content with Silverlight as it often has at least some spaces in folder names.</description>
		<content:encoded><![CDATA[<p>Thanks a lot for the review.<br />
Do you plan to change the restriction on the cross domain Uri?<br />
Now it seems to be no sense in making remote calls to Sharepoint lists content with Silverlight as it often has at least some spaces in folder names.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ilango</title>
		<link>http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview#comment-46278</link>
		<dc:creator>ilango</dc:creator>
		<pubDate>Mon, 11 Aug 2008 08:49:26 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview/#comment-46278</guid>
		<description>I created web service using Rest.It works fine in a single machine.but access from different machine XMLHttpRequest.open("GET","https://192.168.1.2/","true") leave a exception "Access to restricted URI denied" security error.How to overcome it.please give the solution.</description>
		<content:encoded><![CDATA[<p>I created web service using Rest.It works fine in a single machine.but access from different machine XMLHttpRequest.open(&#8221;GET&#8221;,&#8221;https://192.168.1.2/&#8221;,&#8221;true&#8221;) leave a exception &#8220;Access to restricted URI denied&#8221; security error.How to overcome it.please give the solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Handley</title>
		<link>http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview#comment-32445</link>
		<dc:creator>Jeff Handley</dc:creator>
		<pubDate>Fri, 09 May 2008 21:51:41 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview/#comment-32445</guid>
		<description>I didn't see the underscore or dash characters included, and they would need to be included in the allowed set.

Thanks,
Jeff</description>
		<content:encoded><![CDATA[<p>I didn&#8217;t see the underscore or dash characters included, and they would need to be included in the allowed set.</p>
<p>Thanks,<br />
Jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart Carnie</title>
		<link>http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview#comment-31640</link>
		<dc:creator>Stuart Carnie</dc:creator>
		<pubDate>Thu, 01 May 2008 17:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview/#comment-31640</guid>
		<description>Can a path segment of a cross domain request contain parenthesis?

e.g.

http://myhost/base/accounts(A1094)?orderby=Name</description>
		<content:encoded><![CDATA[<p>Can a path segment of a cross domain request contain parenthesis?</p>
<p>e.g.</p>
<p><a href="http://myhost/base/accounts" rel="nofollow">http://myhost/base/accounts</a>(A1094)?orderby=Name</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Gidell</title>
		<link>http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview#comment-31592</link>
		<dc:creator>Mike Gidell</dc:creator>
		<pubDate>Thu, 01 May 2008 03:55:50 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview/#comment-31592</guid>
		<description>My ISP is blocking port 80 so my website is using 8080. I just have my silverlight apps hosted there to show friends and family. Everything works great until i try to use my web service with silverlight. 

As soon as i try to call any WebMethods async call externally it crashes. Everything works internally... Here is what i think is the problem. When i type [my ip]:8080 internally the domain is read as "localhost" externally its read as [my ip]. 

Externally this is a problem because i cannot host anything through just [my ip] it has to be through [my ip]:8080...

I am not sure this is what is happening, but i cannot figure it out. 

Any ideas (other than getting on port 80)?</description>
		<content:encoded><![CDATA[<p>My ISP is blocking port 80 so my website is using 8080. I just have my silverlight apps hosted there to show friends and family. Everything works great until i try to use my web service with silverlight. </p>
<p>As soon as i try to call any WebMethods async call externally it crashes. Everything works internally&#8230; Here is what i think is the problem. When i type [my ip]:8080 internally the domain is read as &#8220;localhost&#8221; externally its read as [my ip]. </p>
<p>Externally this is a problem because i cannot host anything through just [my ip] it has to be through [my ip]:8080&#8230;</p>
<p>I am not sure this is what is happening, but i cannot figure it out. </p>
<p>Any ideas (other than getting on port 80)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Monster</title>
		<link>http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview#comment-31540</link>
		<dc:creator>Mark Monster</dc:creator>
		<pubDate>Wed, 30 Apr 2008 17:36:35 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview/#comment-31540</guid>
		<description>Hmm, just curious is it in the future possible to load the policy-file from a different location? I'm thinking about using Google Picasa Web API. 
http://code.google.com/apis/picasaweb/reference.html#Flash

They have a crossdomain.xml on a different location: http://photos.googleapis.com/data/crossdomain.xml

The best will be a clientaccesspolicy.xml file to be added by Google. But any ideas? There are a lot of Web APIs available but few maybe none have that clientaccesspolicy.xml file on the root.</description>
		<content:encoded><![CDATA[<p>Hmm, just curious is it in the future possible to load the policy-file from a different location? I&#8217;m thinking about using Google Picasa Web API.<br />
<a href="http://code.google.com/apis/picasaweb/reference.html#Flash" rel="nofollow">http://code.google.com/apis/picasaweb/reference.html#Flash</a></p>
<p>They have a crossdomain.xml on a different location: <a href="http://photos.googleapis.com/data/crossdomain.xml" rel="nofollow">http://photos.googleapis.com/data/crossdomain.xml</a></p>
<p>The best will be a clientaccesspolicy.xml file to be added by Google. But any ideas? There are a lot of Web APIs available but few maybe none have that clientaccesspolicy.xml file on the root.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Amundsen</title>
		<link>http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview#comment-31524</link>
		<dc:creator>Mike Amundsen</dc:creator>
		<pubDate>Wed, 30 Apr 2008 13:50:58 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview/#comment-31524</guid>
		<description>That's what I thought and denying consecutive dots is definitely good practice. Thanks for the clarification. URLs that do not have "file extensions" are cool anyway [grin].</description>
		<content:encoded><![CDATA[<p>That&#8217;s what I thought and denying consecutive dots is definitely good practice. Thanks for the clarification. URLs that do not have &#8220;file extensions&#8221; are cool anyway [grin].</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karen</title>
		<link>http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview#comment-31444</link>
		<dc:creator>Karen</dc:creator>
		<pubDate>Tue, 29 Apr 2008 18:06:03 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview/#comment-31444</guid>
		<description>Good clarification.  Single dots are allowed (just not consecutive dots.)  I clarified above.</description>
		<content:encoded><![CDATA[<p>Good clarification.  Single dots are allowed (just not consecutive dots.)  I clarified above.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Amundsen</title>
		<link>http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview#comment-31431</link>
		<dc:creator>Mike Amundsen</dc:creator>
		<pubDate>Tue, 29 Apr 2008 14:08:28 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/15/silverlight-http-networking-stack-part-2-cross-domain-communication-overview/#comment-31431</guid>
		<description>Do I understand correctly that the "." (as in /over/there.xml) is illegal in a cross-domain URI?</description>
		<content:encoded><![CDATA[<p>Do I understand correctly that the &#8220;.&#8221; (as in /over/there.xml) is illegal in a cross-domain URI?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.878 seconds -->
