Comments on: How to bypass cross-domain restrictions when developing AJAX applications http://www.ghidinelli.com/2008/12/27/how-to-bypass-cross-domain-restrictions-when-developing-ajax-applications Thu, 01 Jun 2017 18:51:00 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Joran Greef http://www.ghidinelli.com/2008/12/27/how-to-bypass-cross-domain-restrictions-when-developing-ajax-applications/comment-page-1#comment-54525 Joran Greef Tue, 03 Mar 2009 15:08:19 +0000 http://www.ghidinelli.com/?p=461#comment-54525 Thanks for your post. I've been through the same areas as you in this regard. I've also tried the Apache proxy approach. The problem is it's harder for clients hosting with IIS or shared servers to try this. It also requires more work for your client to interface with your API. The worst, however, is that your latency is effectively doubled, adding on up to 2 seconds per request. In addition, your clients become partner to bandwidth expenses relating to their use of your API. There is an excellent solution discovered by Kris Zyp as recent as July 2008 however: http://www.sitepen.com/blog/2008/07/22/windowname-transport/ I did a quick port of it and have been using it extensively for the past couple of months. It's cross-browser and requires only a small touch of work to your server's api to enable it to respond to cross-domain requests. It doesn't have the same request size limitations as the dynamic script tag hack, and it doesn't have the unbelievable complexity of Google's nested iframe approach which requires chunking to overcome response size limits. Thanks for your post. I’ve been through the same areas as you in this regard. I’ve also tried the Apache proxy approach. The problem is it’s harder for clients hosting with IIS or shared servers to try this. It also requires more work for your client to interface with your API. The worst, however, is that your latency is effectively doubled, adding on up to 2 seconds per request. In addition, your clients become partner to bandwidth expenses relating to their use of your API.

There is an excellent solution discovered by Kris Zyp as recent as July 2008 however: http://www.sitepen.com/blog/2008/07/22/windowname-transport/ I did a quick port of it and have been using it extensively for the past couple of months. It’s cross-browser and requires only a small touch of work to your server’s api to enable it to respond to cross-domain requests. It doesn’t have the same request size limitations as the dynamic script tag hack, and it doesn’t have the unbelievable complexity of Google’s nested iframe approach which requires chunking to overcome response size limits.

]]>