...and so after a long time...
...a random post. could help somebody...

Few things to watch out for while developing browser based apps with cross domain calls.

• If we have an iframe calling another domain (cross domain calling),
  we wont be able to access the parent window and child window documents from each other.
  Instead, we must use postmessage function to communicate with each other.
  
  Sender:
  In parent's page:

  
  var ifrm = document.createElement('iframe');
  
  ifrm.onload = function () {
          if (ifrm.contentWindow.postMessage) {
                  	ifrm.contentWindow.postMessage("some message from parent", targetDomain);
          }
  }
  				
  			

  targetDomain: URL to which message is to be sent.
  Protocol, port and hostname should be an exact match of the targetDomain.
  
  Receiver:
  Now in the targetDomain (in the iframe's page):
  We must have a listener of the type:

  
  addEvent(window, 'message', ParentMessage);
  				
  function ParentMessage(event) { 
  	// This check is a must for sanity and integrity reasons. In a production environment, 
  	// there could be other code doing postmessage (google, facebook etc., does this).
  	// It could interfere with the messages you receive.
          if (event.origin !== OurSourceHostName) {
          	return;
          }
  
  
          //event.data;
  	//event.origin;
  	//event.source;
  
          event.source.postMessage("some message from child", event.origin);
  	// To read this message, the parent window should have a message listener.
  }	
  			

  MDN Postmessage reference

• When using a local development environment, don't use "localhost" or "127.0.0.1".
  Use some other ip address like 192.168.0.1 or some other private ip block address.
  The reason is that IE and Safari wont send SessionId if you use http GET.

2015-Mar-28

...not sure when the next post will be...

I like the slits :). So what about double slits? Lets see some? I am pretty excited.

2015-Mar-29