Contents tagged with AJAX
-
Error 400 with WCF REST Services
I recently worked on a site that had a strange issue where “sometimes” the WCF service (JSON encoding) that we accessed via JavaScript (using jQuery) was throwing an HTTP 400 error. Setting a breakpoint at the web method itself was useless as it would never be hit.
-
Server Controls vs Plugins
-
Getting comfortable with Javascript callbacks
It seems every language has it’s own way of implementing callbacks.
-
Getting excited about AJAX again (but will I use jQuery or Microsoft Ajax 4.0 – or both?)
Dave Reed has a great example of how to do few different things in Preview 5 of Microsoft Ajax 4.0.
-
How JSONP works
There are a plethora of explanations for JSONP (JSON with Padding, I think it stands for) out there – just search for “how JSONP works” and you’ll get a ton of descriptions. JSONP is provided as an alternative to normal JSON by jQuery on the client side to enable the invocation of services outside of the current domain.
-
Minify your Javascripts!
This is a process that is becoming more and more important as we offload a ton of our page processing to .js files as opposed to HTML files processed by the server. This is because we are doing more client templating and logical processing on the client and not on the server.
-
Load jQuery Dynamically
Sometimes you have to load jQuery, but you don’t know if it has already been referenced somewhere else in the website.
-
Using the Generic Dictionary with JSON web services…
If you want to pass a name/value collection of untyped data to a webservice with JSON, do it like this guys, Joost van Schaik, says:
-
Don’t use alert() on AJAX webservice errors!
Even if you want the user to be notified of the fact that an AJAX webservice call has errored out, don’t use an alert() to do it.
-
IIS 7, Dynamic Compression and tons of AJAX web services means massive performance increases