$("#submitBtn").click(function() {
var value = $("#number").val()
console.log('About to run my request...')
$.getJSON("test.cfc?method=double2&returnFormat=json",{number:value},function(d) {
//do nothing with response
console.log('Done with request, it was '+d)
})
})
<html>
<head>
<script src="jquery/jquery.js"></script>
<script>
$(document).ready(function() {
$.ajaxSetup({
beforeSend:function(req) {
console.log('GLOBAL:beforeSend')
},
complete:function(req) {
console.log('GLOBAL:complete')
}
})
$("#submitBtn").click(function() {
var value = $("#number").val()
console.log('About to run my request...')
$.getJSON("test.cfc?method=double&returnFormat=json",{number:value},function(d) {
//do nothing with response
console.log('Done with request')
})
})
})
</script>
</head>
<body>
<input type="text" id="number"> <input type="submit" id="submitBtn" value="Double">
</body>
</html>
No big surprise here. My function's console.log ran first. Then the global beforeSend. Next my callback ran, and when it was done, the global complete ran. I guess this is expected, but it was nice to see it confirmed, and the docs had not made it very clear to me.
Ok, one more example. Last night I blogged a warning to ColdFusion/Ajax developers. ColdFusion has an Ajax security feature by which JSON requests are prefixed with a string, like //. While this works great with ColdFusion's builtin front-end Ajax stuff, it doesn't play well with jQuery and other libraries. While it is easy enough to disable the prefix on the server side, jQuery provides a cool way to handle it as well in the ajaxSetup object. By using the dataFilter function, you can remove the prefix yourself. Consider:
$.ajaxSetup({
dataFilter:function(data,type) {
//remove "//"
console.log(data)
data = data.substring(2,data.length)
console.log(data)
return data
}
})