JsonOrJsonp.cs

var callback = context.HttpContext.Request.QueryString.AllKeys.FirstOrDefault(k => k == "callback");
var data = "{ "key": "value" }"; // JSON payload

if(string.IsNullOrEmpty(callback))
{
    response.ContentType = "application/json";
    response.AddHeader("Access-Control-Allow-Origin", "*";
    response.Write(data);
}
else
{
    response.ContentType = "application/javascript";
    response.Write(string.Format("{0}({1});",context.HttpContext.Request.QueryString[callback],data));
}

one-off.js

var xhr = $.ajax({
    url: 'http://url.to/service',
    data: { prop: 'data' },
    dataType: $.support.cors ? 'json' : 'jsonp'
});

xhr.done(successCallback);

reusable.js

// This sets it globally so you don't have to think about it any more.
// If request is cross domain and cors is not supported, request as jsonp
$.ajaxPrefilter('json', function(options, orig, jqXHR) {
    if( options.crossDomain && !$.support.cors ){
        return 'jsonp';
    }
});

var xhr = $.ajax({
    url: 'http://url.to/service',
    data: { prop: 'data' },
    dataType: 'json'
});

xhr.done(successCallback);

server logic

if request has param 'callback'
	set header "ContentType" = "application/javascript"
	return {callback}(data)
else
	set header "ContentType" = "application/json"
	set header "Access-Control-Allow-Origin" = "*" (or your specific origin)
	return data

So are the one-off.js and the reusable.js essentially accomplishing the same thing?

Yeah. One is a reusable pattern one is a one off.

…

On Feb 7, 2012, at 9:26 PM, Ray ***@***.*** wrote: So are the one-off.js and the reusable.js essentially accomplishing the same thing? --- Reply to this email directly or view it on GitHub: https://gist.github.com/1764347