Slashdot Mirror

← Back to Stories (view on slashdot.org)

An Ajax Reality Worth Worrying About

Posted by ryuzaki0 on from the ajax-world-order dept.

An anonymous reader writes "This article discusses the hype that currently surrounds Ajax and it's shortcomings. Reliable Ajax frameworks are still under construction, and you should worry about navigation history, bookmarkability, feedback, persistence, concurrency, and security. This article will help you avoid the major problems inherent in Ajax development."

4 of 79 comments (clear)

  1. Sessions by shawngarringer · · Score: 3, Insightful

    One thing I wish more webmasters would use on sites with AJAX and other technologies is sessions. When I hit "Back" in my browser, I want it to actually go back... not crap out and dump me completely out.
    I know... I know, I should be using whatever function is built into their website. But, I'm sorry, clicking Back or hitting backspace is just such a habit, its really a deal breaker for me...
    I have no idea how much time I've wasted refilling in forms on my bank's website because it cant figure out what I'm doing when I press back!

    1. Re:Sessions by Dionysus · · Score: 3, Interesting

      The BankofAmerica website even works with Konqueror.

      --
      Je ne parle pas francais.
  2. Re:Blame HTTP Post by heinousjay · · Score: 3, Informative

    You don't need anything other than HTTP to support applications that don't require a constant connection. The redirect-after-post technique does what you're looking for. It allows the browser view to always reflect model state, which is (or should be) the end goal.

    --
    Slashdot - where whining about luck is the new way to make the world you want.
  3. Ajax is not the problem by Umbral+Blot · · Score: 4, Insightful

    The real problem with Ajax isn't java script or browser fickleness, or Microsofts hatred of standards, it is that we are trying to solve one a problem, distributed applications over the internet, within the wrong framework, a document viewer with scripting capabilities. What we really need is an internet application browser, that is desgined to be able to host such applications, render consistantly over multiple platforms, be stable and secure, ect. Then users wouldn't be confused concerning the behavior of the back button for example, because no one expects applications to have a back. It might make sense to have the broweser be able to launch the application viewer when needed, but more than that is just begging for problems.

    --

    Philosophy.