- From: Thomas Steiner <tomac@google.com>
- Date: Sat, 7 Jul 2012 09:56:37 +1000
- To: Henry Story <henry.story@bblfish.net>
- Cc: Read-Write-Web <public-rww@w3.org>, Michael Hausenblas <michael.hausenblas@deri.org>, Nathan Rixham <nathan@webr3.org>
[pruned to: list, added CORS-enabled folks I know] Hi Henry, Thanks for putting this service online (in the form of source code) and also to the folks over at data.fm for making it actually available as a publicly callable service. Services like YQL allow you to turn any website in a JSON-P API, which—while less elegant—in practice serves the same purpose as CORS: "overcome" the SOP. I have used YQL widely in some of my Linked Data apps, however, always have hit the call limit per time unit. Even on my private hosted server (1&1, so a hoster with a name), where I used to host a PHP proxy, I have hit some of their DDoS triggers, so after a while started returning 500 errors. Do you have a solution or view to/on that issue? It is in my humble opinion one of the main stumble stones to all that beautiful Linked Data tales. As soon as you seriously stat to follow the links, the infrastructure goes down (per security design). Looking forward to some opinions, and sorry if this sounds too negative or unrelated to your service announcement. I _appreciate_ any and all efforts towards enable-cors.org! Best, Tom Thank God not sent from a BlackBerry, but from my iPhone
Received on Friday, 6 July 2012 23:57:10 UTC