<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:pingback="http://madskills.com/public/xml/rss/module/pingback/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Eran Nachum's Blog</title>
    <link>http://www.eranachum.com/</link>
    <description>www.eranachum.com - Implementing &amp; executing my thoughts...</description>
    <language>en-us</language>
    <copyright>Eran Nachum</copyright>
    <lastBuildDate>Tue, 04 Sep 2012 21:27:00 GMT</lastBuildDate>
    <generator>newtelligence dasBlog 1.8.5223.2</generator>
    <managingEditor>eranachum@hotmail.com</managingEditor>
    <webMaster>eranachum@hotmail.com</webMaster>
    <item>
      <trackback:ping>http://www.eranachum.com/Trackback.aspx?guid=c7a2254c-e654-4450-b69b-d5c55efd092a</trackback:ping>
      <pingback:server>http://www.eranachum.com/pingback.aspx</pingback:server>
      <pingback:target>http://www.eranachum.com/PermaLink,guid,c7a2254c-e654-4450-b69b-d5c55efd092a.aspx</pingback:target>
      <dc:creator>eranachum@hotmail.com (Eran Nachum)</dc:creator>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
      Hi,
   </p>
        <p>
      The cross domain is a well know issue when trying to work between 2 or more domains
      under the same web page.
   </p>
        <p>
      For an example, you developed a great third party control (or some other web component)
      that suppose to affiliate with another web site and hosted it inside an iframe on
      the host web site, but when giving the ability for the common user to do some actions
      inside your cross domain iframe, you find yourself in a problem because the host web
      site bans all the requests from the iframe itself.
   </p>
        <p>
       
   </p>
        <p>
      This is a very common cross domain problem, that is being exists in some browsers
      in order to perform security policy.
   </p>
        <p>
       
   </p>
        <p>
      I found lately a great open source code that can solve your problems very easily called: <strong>easyXDM</strong>. 
   </p>
        <p>
      According to their site: <em>“easyXDM is a Javascript library that enables you as
      a developer to easily work around the limitation set in place by the Same Origin Policy,
      in turn making it easy to communicate and expose javascript API’s across domain boundaries.”</em></p>
        <p>
          <em>
          </em>
        </p>
        <p>
      You can find some code examples and how-to techniques on their web site <a href="http://easyxdm.net/wp/" target="_blank">here</a>.
   </p>
        <p>
       
   </p>
        <p>
      Have fun and good luck!
   </p>
        <img width="0" height="0" src="http://www.eranachum.com/aggbug.ashx?id=c7a2254c-e654-4450-b69b-d5c55efd092a" />
      </body>
      <title>Cross Domain URL Access from Iframe using Javascript &amp;ndash; Great Solution</title>
      <guid>http://www.eranachum.com/PermaLink,guid,c7a2254c-e654-4450-b69b-d5c55efd092a.aspx</guid>
      <link>http://www.eranachum.com/PermaLink,guid,c7a2254c-e654-4450-b69b-d5c55efd092a.aspx</link>
      <pubDate>Tue, 04 Sep 2012 21:27:00 GMT</pubDate>
      <description>&lt;p&gt;
   Hi,
&lt;/p&gt;
&lt;p&gt;
   The cross domain is a well know issue when trying to work between 2 or more domains
   under the same web page.
&lt;/p&gt;
&lt;p&gt;
   For an example, you developed a great third party control (or some other web component)
   that suppose to affiliate with another web site and hosted it inside an iframe on
   the host web site, but when giving the ability for the common user to do some actions
   inside your cross domain iframe, you find yourself in a problem because the host web
   site bans all the requests from the iframe itself.
&lt;/p&gt;
&lt;p&gt;
   &amp;#160;
&lt;/p&gt;
&lt;p&gt;
   This is a very common cross domain problem, that is being exists in some browsers
   in order to perform security policy.
&lt;/p&gt;
&lt;p&gt;
   &amp;#160;
&lt;/p&gt;
&lt;p&gt;
   I found lately a great open source code that can solve your problems very easily called: &lt;strong&gt;easyXDM&lt;/strong&gt;. 
&lt;/p&gt;
&lt;p&gt;
   According to their site: &lt;em&gt;“easyXDM is a Javascript library that enables you as
   a developer to easily work around the limitation set in place by the Same Origin Policy,
   in turn making it easy to communicate and expose javascript API’s across domain boundaries.”&lt;/em&gt;
&lt;/p&gt;
&lt;p&gt;
   &lt;em&gt;&lt;/em&gt;
&lt;/p&gt;
&lt;p&gt;
   You can find some code examples and how-to techniques on their web site &lt;a href="http://easyxdm.net/wp/" target="_blank"&gt;here&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
   &amp;#160;
&lt;/p&gt;
&lt;p&gt;
   Have fun and good luck!
&lt;/p&gt;
&lt;img width="0" height="0" src="http://www.eranachum.com/aggbug.ashx?id=c7a2254c-e654-4450-b69b-d5c55efd092a" /&gt;</description>
      <category>AJAX;JSON;Javascript</category>
    </item>
    <item>
      <trackback:ping>http://www.eranachum.com/Trackback.aspx?guid=7f7734e4-20df-4054-995d-e321ad923f61</trackback:ping>
      <pingback:server>http://www.eranachum.com/pingback.aspx</pingback:server>
      <pingback:target>http://www.eranachum.com/PermaLink,guid,7f7734e4-20df-4054-995d-e321ad923f61.aspx</pingback:target>
      <dc:creator>eranachum@hotmail.com (Eran Nachum)</dc:creator>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
      Great post in regards asp.net &amp; Json.
   </p>
        <p>
      I wasn’t familiar with <a title="System.Web.Script.Serialization.JavaScriptSerializer" href="http://msdn.microsoft.com/en-us/library/system.web.script.serialization.javascriptserializer.aspx" target="_blank">System.Web.Script.Serialization.JavaScriptSerializer</a> which
      provides serialization and deserialization functionality for AJAX-enabled applications.
   </p>
        <p>
      While searching the web in regards this issue, I bumped into a great post that outlines
      the usage of this namespace.
   </p>
        <p>
      You can check it out <a href="http://blogs.msdn.com/b/rakkimk/archive/2009/01/30/asp-net-json-serialization-and-deserialization.aspx" target="_blank">here</a>.
   </p>
        <p>
      Good Luck.
   </p>
        <img width="0" height="0" src="http://www.eranachum.com/aggbug.ashx?id=7f7734e4-20df-4054-995d-e321ad923f61" />
      </body>
      <title>ASP.NET &amp;ndash; JSON &amp;ndash; Serialization and Deserialization</title>
      <guid>http://www.eranachum.com/PermaLink,guid,7f7734e4-20df-4054-995d-e321ad923f61.aspx</guid>
      <link>http://www.eranachum.com/PermaLink,guid,7f7734e4-20df-4054-995d-e321ad923f61.aspx</link>
      <pubDate>Mon, 28 Jun 2010 14:34:00 GMT</pubDate>
      <description>&lt;p&gt;
   Great post in regards asp.net &amp;amp; Json.
&lt;/p&gt;
&lt;p&gt;
   I wasn’t familiar with &lt;a title="System.Web.Script.Serialization.JavaScriptSerializer" href="http://msdn.microsoft.com/en-us/library/system.web.script.serialization.javascriptserializer.aspx" target="_blank"&gt;System.Web.Script.Serialization.JavaScriptSerializer&lt;/a&gt; which
   provides serialization and deserialization functionality for AJAX-enabled applications.
&lt;/p&gt;
&lt;p&gt;
   While searching the web in regards this issue, I bumped into a great post that outlines
   the usage of this namespace.
&lt;/p&gt;
&lt;p&gt;
   You can check it out &lt;a href="http://blogs.msdn.com/b/rakkimk/archive/2009/01/30/asp-net-json-serialization-and-deserialization.aspx" target="_blank"&gt;here&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
   Good Luck.
&lt;/p&gt;
&lt;img width="0" height="0" src="http://www.eranachum.com/aggbug.ashx?id=7f7734e4-20df-4054-995d-e321ad923f61" /&gt;</description>
      <category>ASP.NET;C#;JSON</category>
    </item>
  </channel>
</rss>