. I haven't tested it because it requires the source and target of both domains to set up specific DNS records and uses a sub-domain. This requires quite some expertise and disables the retrieval of data from user given sources.The other one goes by the name of JSON
to this problem. It uses a XML type of syntax and adds the contents of the file as a CDATA block. Un-very-fortunately... E4X (the protocol allowing this trick) is not supported by explorer
and probably other browsers. So that's not gonna fly.But I was on the right track. The correct track is JSON. The two leaders currently implementing JSON are Google
.Unfortunately JSON is very dependent on serverside scripts and/or very specific syntax. That means you have to either adjust the file line by line manually or that your server will still serve as a proxy. That's kind of what we're trying to avoid.Thus ends my search and do I give up, for now. Maybe we'll be able to easily request offsite data once developers realize the futility of current security restrictions since there are many ways to bypass it.