I'm working on a thin client application which will be used by
multiple users concurrently and I'm having problems wrapping my head
around how we'll address overwriting of data that's being edited by
another user. Since this application will be using a lot of Ajax-type
interactions it will allow users to change individual attributes of
objects. In this case, the objects are financial data, so making sure
the user knows what the most up-to-date value (OR correct value --
these are two distinct options) is is of very high importance.
Does anybody have an example of the web-site for
ticket/flight/hotel/car reservation with one-page interaction model,
possibly based on Ajax? That means the user doesn't have to fill out
the form in several steps, instead, he can select everything he wants
on one single screen.
So, they've updated the Apple Store. And in addition to new
PowerBooks and Dual dual-core G5s, there's a bit of AJAX going on.
I was shopping for a new PowerBook (got a 1.25Ghz I need to get rid
of if anyone's interested) and as I upgraded the HD to 120G, I
noticed something going on in the top right corner - there was a JS
fade technique to call my attention to the updated list of features
(new HD size) and updated total of my shopping cart.
I thought it might be a fluke, or maybe the page just reloaded really
Anyone have any ideas what impact AJAX has on 508 compliance? How
easy/difficult it is to make it 508 compliance? Many screen readers
only reread the page upon page loads (or used to). Has this changed?
Yet another challenge in the RIA bucket - but I still think they're