Friday, 7 September 2007

AJAX & Web 2.0 Tutorial (Section 5) - Applications

  1. If you ask someone what Ajax stands for, they might answer it doesn’t stand for anything, or they might say “Asynchronous JavaScript And XML”
  2. Asynchronous means that you’re welcome to send requests one after another, but they’re not guaranteed to return in that order (really, they’re not guaranteed to return at all, but that’s rare)
  3. Server load affects your scripts in two similarbut different ways, including:
    1. Everything gets slower
    2. Different parts of things get slower (So some scripts that originally took similar amounts of time can now take drastically different amounts of time)
  4. While Ajax encourages more communication between client and server, it’s generally the same information you would provide anyways, developers simply need to maintain their normal level of vigilance.
  5. There are many situations within Ajax applications where this is sub-optimal
  1. A user could enter invalid login credentials, then hit the login button. Realize their mistake correct it then hit it again
  2. Select something from a list to have further information populated by Ajax, then select another item
  3. A user could click a button to login, then activate another page element that requires them to have logged in before access

No comments: