Since my last post of when to use AJAX, a lot has changed in the ways of AJAX programming. New tools, ideas, and techniques are constantly being developed to support this latest and greatest craze.
Some developers just want use the latest buzzwords and technologies in their applications just to prove that they can build such a beast. Sort of like an "I climbed Mt. Everest" battle cry.
However, most applications shouldn't be built completely with AJAX from the ground up. Of course, AJAX and DHTML are two completely different animals. But that's another post altogether.
This is absolutely great news for Dojo users.
Everyone has been asking "Where's the grid widget?" since Dojo 0.9 was first released (I was one of them). That question has been answered through a press release declaring that the TurboGrid will be released in the 1.0 version of Dojo.
One question I had answered was is it going to be the professional version or the free version? And then I came across this blog post where the press release was posted as well.
When you start building your web application from the ground up, it's best to think about security immediately.
Aleksey Shevchenko, over at Developer.com, submitted an article called AJAX Security, which talks about the different types of AJAX attacks and provides tips on how to programatically prepare yourself for such attacks.
Over the weekend, I came across a site that hosts a lot of AJAX techniques that are quite useful, I particularly like the charting feature.
Very cool site!
I've been using AJAX since I saw the first post from Jesse James Garrett and I've never looked back. It's a technology that is definitely here to stay.
Being a programmer is great, but trying to convince upper management as to why AJAX should be used on the next project is a bigger undertaking than writing an application.
If you are still looking for that reason to implement AJAX into your project, Agile AJAX provides 10 business reasons to use AJAX in your application.
IBM started a series on Mastering AJAX way back in January and I reported on it rather quickly.
I just wanted to keep everybody up to speed on the series and that they were on Part 10. Wow, long series.
Definitely a good move towards standards.
For most developers, AJAX web development is a rush, because it's a relatively new way of creating web applications. It actually blurs the lines between a desktop application and a web application.
Bu when should you use it? and why?
Since Atlas (Microsoft's AJAX implementation) has been released as beta, Scott Guthrie has posted an excellent technique on his blog about how to call the server using AJAX, return a web user control for the UI to render, and update a non-updatable panel.
His method uses a simple web service and he describes that this technique reduces code to about ~20 lines of code. He is basically moving the Web User Controls out of the UI and into the server. The web control's string is passed back to the client.
Ajaxian.com has some updated news about the beta release of Atlas.