Web applications are easy to use, manage and to deploy. A web application runs on every desktop. The name "application" is a not the right description for what happens. We are shipping documents. (http is the shipper). With Ajax comes a new wave. Ajax trys to split a document in a part time communication. Instead of shipping the whole document, send parts and replace the result in the browser. This may be helpfull in some cases but didnt solve the base problem. We are not always connected. We are not allways on the same device- but we are always the same guy with the same intrest and job. .
From my understanding AJAX should be completed with a offline part. This kind of technologie exists for a long time like HTML Applications. Windows Script can use jscript instead of vb script. But no new framework, only implement it in ATLAS and have propertys like offlinecache=true and Scriptmanager needs like installlocal=true. Also the ship method should not be relevant
Its like AJAX: verything exists before, but now its easy and common. Yahoo seems to go in this direction. (konfabulator)
The use case is: i am sitting in the plane and want to order a book. I have already done this before and its like ajax with a static html page and callbacks. Instead callbacks, local cache is used. When i am online again, browser detects that and show me open transactions. I commit it to execute.
to visionary?
to give it a buzz word: Async HTML Offline Application ( AHOA)