Add JSONP Support

[septerr]

This stemmed from the discussion here: https://groups.google.com/forum/#!topic/locomotivecms/uFpFDkG_gqw

Rest calls from Javascript to get an auth token (to later query for other things) fails because of browser restrictions on scripts that fetch data from domains other than their original domain. There is a way around this if the service you are querying for data supports JSONP.

This issue is to add JSONP support to locomotive.

[markwpearce]

I want to get cross domain data-sharing working through locomotive, too.

So, if we were to implement JSONP, is the idea is that a call to:

<script type="text/javascript" src="http://mysite.com/locomotive/api/content_types/things/entries.json?callback=someFunction">
</script>

respond with:

someFunction( {the json of all the 'things' content entries} );

regardless of if the caller has an authenticated token?

[septerr]

Yes. Did pointed this page - http://www.nolanevans.com/2011/03/adding-jsonp-support-to-your-rails-app.html for explanation of how we might do this.

I no longer need this for my project. I am using Net::HTTP in my rails app to request for the entries on the server side instead of client side JavaScript.

[hems]

this might help: http://blog.carbonfive.com/2012/02/27/supporting-cross-domain-ajax-in-rails-using-jsonp-and-cors/

[did]

I'm closing it without a patch because support for jsonp is pretty straightforward as described in the articles and should be added to the main app instead. It's just a matter of including the gem and insert the right middleware.