Cross-Domain AJAX versus JSONP - CDA Cross Domain AJAX package blog

Contents

Conclusions

Introduction to Cross-Domain AJAX

Whenever I need to load JavaScript application components from the Web server, I usually insert a JavaScript tag in the Web page document and used some "dirty" tricks to execute it.

Cross-Domain AJAX uses this approach to implement a cleaner solution wrapped as a jQuery plug-in.

Cross-Domain AJAX advantages over JSONP

1. JSONP requires that the server responds with JSON data

JSONP requires that the server returns JSON data wrapped around a padding function to process that data.

Therefore you need to provide the function on the browser side that still needs to process the JSON data to do something useful with it.

Cross-Domain AJAX does not need any JavaScript code to be previously loaded on the browser to process the server response. The JavaScript code that is loaded simply executes by itself, so all the application logic is delivered from the server.

For example, you can start displaying of syndicated videos. If you were searching for content, JSONP cannot do more by itself then delivering the search results, but not retrieve and execute application that actually processes the results.

If you expect that the response may fail to be returned by the server, you can even set a timeout value, after which you may retry and call the server again. This is easily accomplished by the waiter helper.