AJAX in demand?

[dang65]

The last three contracts I've done have used AJAX extensively, but not for anything whizzy - stuff like smoothing out form filling by dynamically filtering select options, or taking people through online training courses without constant browser refreshing, or updating scores on tests etc.

I think it's used very widely for useability tricks like that. As mentioned before, much of the AJAX capability was around for a few years before the name was made up, and the vast majority of web users have been using it for a long time without noticing. It's only when something like Google Maps comes along that people start wondering how they manage to fit all those maps into your computer like that and how clever the web is these days.

[basshead]

If you are a competent web developer you should be used to writing sites that use both client and server side verification to prevent security issues caused by users turning off JavaScript anyway.

It should be pointed out that the issue goes far beyond validation. Its about degrading gracefully with different browsers, devices and users (accessibility) so the lowest common denominator will always be plain XHTML.

Approaching sites from that point of view ensures the widest audience. Developers like to put the whizzy AJAX stuff on the screen first though, often driven by a need to impress the customer early in the lifecycle.

[Jaws]

That's probably my preferred route too. So if the extenders degrade satisfactorilly, maybe I've little to be worried about.

For asp.net, these extenders just inject javascript within script blocks using the scriptmanager control whic just subscribe to events on your html controls. Without javascript enabled they just won't subscribe (and the events will not be fired for that matter) so therefore you can use them quite safely either way.

[PAH]

not that it would not function without AJAX considering I've mainly been making use of control extenders which make async callbacks to add functionality.

That's probably my preferred route too. So if the extenders degrade satisfactorilly, maybe I've little to be worried about.

can't see the benefit for your standard web apps which aren't completely driven by AJAX.

I get the feeling it's just a fad and will be replaced by other evolutions such as Silverlight or whatever else the next versions of the browsers will support.

Currently feels like XML did when everyone was trying to use that for scenarios where it's a lot simpler and sensible to just use other solutions that are already established and supported.

People are used to browsers and how they work (click something and wait for it to respond), so until we get stuff that allows true offline internet (like Google are working on) what we have at the moment is just an interim improvement for some client experiences, such as live updates.

[Jaws]

When I was last looking for work I had someone insisting I knew a little ajax to be put forward so there must be a demand for it. I also notice it in quite a lot of commercial websites more and more these days (the search autocomplete thing pops up all over the place now).

I've been making use of it on my current project. Luckily for me it's an internal app so I can be sure of javascript on the client, not that it would not function without AJAX considering I've mainly been making use of control extenders which make async callbacks to add functionality.

I've got this book on AJAX although I haven't yet felt the need to read it as it's not something that features extensively in my pages (I really couldn't be arsed to build up an entire application that runs within a single page for instance). I think maybe a book would be useful if you're working in a media type company, can't see the benefit for your standard web apps which aren't completely driven by AJAX.

[PAH]

async jscript & xml ?

Close enough. Except Microsoft are reported to be using JSON instead of XML for the messaging.

Is JSON something else I need to find an ebook for?

[PAH]

Seriously, are you stuck in the 90's ???

Obviously I am, seeing as the core technologies behind AJAX have been available since then.

I've been able to get by quite nicely without it so far, but wonder if the demand is now there where it would be a big benefit to have it in my skill-set, or if it's still only just catching on and there are still some big obstacles stopping the big boys from relying too heavily on it.

I can only think of a handful of well known public sites that make obvious use of AJAX to improve the user experience. Maybe I've got javascript switched off!

[miffy]

Do you know what AJAX stands for ?

async jscript & xml ?

or it's a damb good floor cleaner!

[PAH]

Do you know what AJAX stands for ?

Yes I do.

I suppose they mean they're going to leave a backdoor so some javascript works, but god knows how they're going to do it.

[Ardesco]

I suppose I ought to write a bit more as well. All the web 2.0 stuff is based on AJAX and I would expect all user friendly sites to pick it up and use it in the future.

If you are a competent web developer you should be used to writing sites that use both client and server side verification to prevent security issues caused by users turning off JavaScript anyway.

Seriously, are you stuck in the 90's ???

[Ardesco]

Done a bit of playing around with AJAX, particularly the extensions available with .Net.

I can see the attraction of it but is it's dependency on javascript a serious issue when people can still turn off javascript processing in their browser?

I think I read that IE7 and future releases will get around this so even if the user switches off javascript, the ajax stuff will still work. If true, what about Firefox and other browsers that are still in general circulation?

I don't fancy going down the road of having to develop AJAX and non-AJAX versions of web pages if that's still a necessity. What do clients usually require on this front?

Just not sure I should devote any time to AJAX unless there is going to be a genuine need and benefit for it on my CV, alongside the usual .Net technologies.

Do you know what AJAX stands for ?

[PAH]

Done a bit of playing around with AJAX, particularly the extensions available with .Net.

I can see the attraction of it but is it's dependency on javascript a serious issue when people can still turn off javascript processing in their browser?

I think I read that IE7 and future releases will get around this so even if the user switches off javascript, the ajax stuff will still work. If true, what about Firefox and other browsers that are still in general circulation?

I don't fancy going down the road of having to develop AJAX and non-AJAX versions of web pages if that's still a necessity. What do clients usually require on this front?

Just not sure I should devote any time to AJAX unless there is going to be a genuine need and benefit for it on my CV, alongside the usual .Net technologies.