Comments on: Ajax spurs Web rebirth for desktop apps
Watch out, Office. New tools and techniques are fueling a surge in hosted versions of traditional PC software.
Watch out, Office. New tools and techniques are fueling a surge in hosted versions of traditional PC software.
January 2, 2010 6:26 PM PST
January 2, 2010 4:56 PM PST
January 2, 2010 4:16 PM PST
Add headlines from CNET News to your homepage or feedreader.
More feeds available in our RSS feed index.
Related quotes
http://www.sundialsystems.com/articles/workspaceondemand.html
in fact, if anything, it was invented by Netscape/Sun when they introduced javascript and liveconnect.
IE dabbled with Remote Data Script(Not great security wise).
Microsoft is definetly deserves some credit for AJAX.
Google deserves credit for making it popular.
you use in the application are essentially published for others to
read as they wish. Many organizations look at this as access to
provide targeted ads, But that's about the most benign option.
Security is totally shot to h--- in this approach.
I don't intend to get paranoid about it, but I'll stick with
applications that aren't built to blab.
Early versions of Netscape supported JavaScript. This is the technology that really created opportunities to bring the browser to life. Combining JavaScript and HTML created a number of ways to communicate with the server asynchronously. One way was to use hidden frames and do form submits. Form submissions thru hidden frames allowed sending and receiving information without the user experiencing page reloads. Another way is to take advantage of the capability to dynamically load images. The capability was created for image rollovers, but you could co-opt this capability via a technique called "GIF data pipes" (http://depressedpress.com/Content/Development/JavaScript/Articles/GIFAsPipe/Index.cfm) By attaching cookies or query string parameters to the request for an image you could communicate with the server and the server could respond by sending cookies down with the new image.
JavaScript provided a number of ways to render content on pages. The earliest that I am aware of is "document.write()". I used to call this poor mans DHTML because it worked in nearly every browser even Netscape version 2. The capabilities in browsers have definitely evolved for the better. NS 4 introduced layers, they were limited in functionality, but wow were they exciting at the time. With the later introduction, IE 4 Microsoft introduced some eye popping DHTML capabilities.
My point is that even with old non-Microsoft technology you could AJAX. I totally agree that Microsoft took these technologies and enhanced them, but they by no means invented them. I'm sure there are earlier examples of this capability, I just wanted to point out that in browsers this capability has been around for quite some time.
Another point is that developers didn't just realize that AJAX was great; many have known it since the Netscape 2 days. The problem is that users had all sorts of browsers. Some supported X some supported Y other didn't even know what X & Y were (links anyone?). When google released google maps it was just an "ah-ha" moment. All of the sudden the mantra beaten into web developers heads: "build to the lowest common denominator" seemed very outdated. We still though of the lowest common denominator as NS 3 or NS 4. The real change here is that people have upgraded their browsers. Now we can pretty much be assured that the user is running IE 5 -6, Firefox 1.x, Safrai, Opera, KHTML or some other browser with all these great capabilities. Consumers of the web have been slowly changing browsers all these years, the thing is we just noticed it all at once.
Regards,
-eric
>> tools will continue to exist for
>> sophisticated tasks, but AJAX fits the
>> need for simpler jobs
Not quite.
AJAX not only revives the user experiences, but also explores better programming models that make sophisticated app easy to develop.
The ZK project, an open-source Web framework, is an example. Details at http://zk1.sourceforge.net and demo at http://www.potix.com/zkdemo/userguide.
http://en.wikipedia.org/wiki/Ajax_%28programming%29
http://en.wikipedia.org/wiki/XMLHTTP
mj
http://www.junglemungle.com
- An article about this topic
- by orencs March 12, 2007 3:57 PM PDT
- A Software Architecture Toolset for Choosing the Right Type of Client Application
- Like this Reply to this comment
-
(15 Comments)Choose "web application" or "desktop application"? Rich-Internet or a Smart-Client Application?
http://www.codeguru.com/csharp/csharp/cs_misc/designtechniques/article.php/c13369/
by Oren Cohen Shwartz