Question to authors: Will AJAX kill web frameworks?

[Debashish Chakrabarty]

A blog entry here recently raised this interesing issue. AJAX has, sort of, shifted the focus to the client-side functionality that even existing frameworks are now talking of providing support. Yet, I wonder, whether there would be an exodus from traditional frameworks due to AJAX. What if the user is averse to using Javascript and disables it? You would need to have a provision for a HTML based traditional system in your backup plan. What do you people think?

A second unrelated question is about security. How safe is it for a user to perform an e-commerce transaction and type-in his credit card details over an AJAX enabled app on his browsers?

Thanks a lot,

[Ryan Asleson]

Personally, I don't see Ajax displacing the current Web MVC frameworks. Ajax still communicates with the server using the request-reponse paradigm over HTTP, so those Web frameworks that hide a lot of those details for us will remain just as important in the Ajax world.

As Ajax becomes more popular the Web frameworks are sure to evolve to better support Ajax, but I just don't see them going away because of Ajax.

[Eric Pascarello]

check out this article on Ajaxian: http://www.ajaxian.com/archives/2005/11/is_ajax_gonna_k.html

Eric

[Nate Schutta]

I second what Ryan said - Ajax works *with* your favorite framework. While I'm sure some people will eject Struts or whatever from their office, I just can't see the reason to abandon them. Afterall, you still need something to dish up the initial page and the subsequent bits and pieces. I do think that the frameworks will change though to facilitate Ajax...