Blog DeraiBali.com

When working with an Ajax-enhanced website, it’s generally a good idea to provide a regular request fallback for any core functionality of the site. When you work to ensure that a fallback is in place, you will be faced with determining when a particular request is an Ajax request or just a normal page request. In most situations, it’s considered a best practice to build your site without Ajax first, adding the Ajax functionality afterward so the fallbacks are in place from the beginning.

Fortunately, jQuery makes it super easy to differentiate the Ajax requests from normal page views.

Two years ago I made the somewhat immodest claim that 2007 would be the “Year of jQuery.” Since then, jQuery’s popularity has grown in ways that none of the core contributors could have imagined. Now I’m ready to make another bold pronouncement: 2009 will be the year of jQuery UI. Here’s why:

As many of you have discovered by now, jquery.com and its subdomains have been offline intermittently over the past several weeks. On behalf of the jQuery Project Team, I apologize for any inconvenience this has caused.

John Resig is aware of the problem and is working with the hosting company to get things resolved as quickly as possible. In the meantime, Remy Sharp, who runs jQuery for Designers, has graciously provided a few alternatives for API documentation:

This is the first thing to learn about jQuery: If you want an event to work on your page, you should call it inside the $(document).ready() function. Everything inside it will load as soon as the DOM is loaded and before the page contents are loaded.