On Tue, Nov 3, 2009 at 05:24, David R. Karger <[email protected]> wrote: > > Note that the s-w.org examples use relative links to point to the data, > which obviously won't work if you download the file. I presume you mean > you are updating them to absolute links. > > Note also that modern browsers' cross-site-scripting protections > _forbid_ accessing data on a different server than the one containing > the root page. So the data fetch fails, which leads exhibit to throw a > syntax error---clearly not the most informative possible. To get around > that, you can use exhibit's "jsonp" framework (a standard mechanism for > circumventing the XSS protections). But this does require modifying the > link specification (you need application/jsonp instead of > application/json) and you need to be talking to a server that knows how > to service jsonp requests. I don't know if s-w.org does. If you aren't > so lucky, you can use our babel server as a proxy---you can point it to > a json file, and it will give you a url that will serve up that file > encapsulated as jsonp.
Hiya. I thought it might be the cross-server scripting problem. Is there something you can point me to that explains the differences between json and jsonp? Putting both files on the same server and using a relative link "/foo.json" worked perfectly, but it would be good to know about jsonp. Thanks, -James --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SIMILE Widgets" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/simile-widgets?hl=en -~----------~----~----~----~------~----~------~--~---
