So then since the cross domain scripts are fetched by adding a script tag.
All of the above methods for turning caching on/off via the ajax settings do not apply? The cross domain script acquisition appears to ALWAYS have the cache busting on. Is there a place to request as a feature maybe in next release - or when appropriate - a new parmenter for $.getScript() that could turn off cache busting even for the cross domain case. Thanks! Joe On May 15, 12:28 pm, "Mike Alsup" <[EMAIL PROTECTED]> wrote: > > Can you clarify if - in FACT- setting cache:true will affect > > $.getScript() when it is getting the script from a different domain? > > (and perhaps what technique $.getScript uses under the covers for the > > cross domain case?) > > > Also - the direct use of the cache parameter in an $.ajax( options) - > > call - certainly will not work Cross Domain right? > > > Is there a reason there cannot be a separate cache parameter in > > $.getScript() in future that handles both same domain and cross domain > > cases? > > The answers are in the code. > > $.getScript calls $.ajax (via $.get) > $.ajax always uses $.ajaxSettings for default settings > $.ajax always turns off caching when requesting scripts > cross domain scripts are fetched using a script tag > same domain scripts are fetched via XHR
