Monday, August 22nd, 2005

State of Ajax: Progress, Challenges, and Implications for SOAs

Category: Editorial

Dion Hinchcliffe has written a fairly comprehensive view of the current developments, progress, and general state of affairs with Ajax and its techniques and available tools.

Also, for corporate application development and architects, the article goes into the current known implications of Ajax and Service-Oriented Architectures, which will affect each other considerably as they evolve.

Dare Obasanjo also got into the mix:

Problems that have to be solved [or at the very least considered] include

  1. How to abstract away browser detection from each page in the application
  2. How to make the site accessible or at least work on non-Javascript enabled browsers
  3. How to efficiently manage the number of connections to the server created by the client given the “chattiness” of AJAX applications compared to traditional web applications
  4. How to reduce the amount of time spent downloading large script files
  5. How to create permalinks to portions of the application
  6. How to preserve or at least simulate the behavior of the browser’s ‘Back’ button

More resources:

Scott Isaacs: Why Ajax is so 1999? Part 1, and Part 2.


Posted by Dion Almaer at 6:23 pm
Comment here

3.3 rating from 6 votes

Comments Here »

Comments feed

Leave a comment

You must be logged in to post a comment.