You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JSONP is a "hack" that allows cross site calls without using CORS (although I believe its capabilities are limited). It has been suggested that it'd be useful for fluidinfo.js to support JSONP calls (see https://twitter.com/#!/renedudfield/status/102723431413452800).
I suggest a flag is passed at time of instantiation to indicate the library should use JSONP for cross-site calls rather than the default CORS method:
fi = fluidinfo({username: "username", password: "password", jsonp: true});
If I remember correctly, any fix will also need access to the DOM in order to make the JSONP hack work.
Finally, it should be opaque to the user how we're making the call to Fluidinfo (either CORS or JSONP). Their main concern is that the damn thing works. :-)
The text was updated successfully, but these errors were encountered:
JSONP is a "hack" that allows cross site calls without using CORS (although I believe its capabilities are limited). It has been suggested that it'd be useful for fluidinfo.js to support JSONP calls (see https://twitter.com/#!/renedudfield/status/102723431413452800).
I think this is a good idea since JSONP works on a wider range of browsers than CORS does. Also, Fluidinfo appropriately supports JSONP calls to it (see http://doc.fluidinfo.com/fluidDB/api/http.html#support-for-jsonp).
I suggest a flag is passed at time of instantiation to indicate the library should use JSONP for cross-site calls rather than the default CORS method:
If I remember correctly, any fix will also need access to the DOM in order to make the JSONP hack work.
Finally, it should be opaque to the user how we're making the call to Fluidinfo (either CORS or JSONP). Their main concern is that the damn thing works. :-)
The text was updated successfully, but these errors were encountered: