These days everyone is talking about AJAX. It's supposed to be a cool way of creating Web applications.
Tutorial Details:
The idea is noble: instead of rendering an entire HTML page on each little change on the page, it?s much better to send an asynchronous request that will get the data for you and refresh only the relevant portion of the screen. Every author writing on AJAX is giving the same (the only? ) examples where this technology is being used: Google maps and email. (BTW, I?m a little sick of these examples). Since I?m not going to be helping Google in improving their maps, I?d like to see some real-world examples implementing this technology. Ajax proponents will immediately come with this exciting example of how great it is to refresh some screen info as the user enters character in a text field. And here's a sample conversation that might have happened between an imaginary AJAX supporter and myself.
Wow! I like it? as long as you do not have to be a rocket scientist to program this functionality. But wait a minute, do not you think that any entry level Visual Basic/PowerBuilder/Java programmer can do the same thing easily? AJAX applications have to rely on JavaScript, assume the expert knowledge of this not-so-interesting language, different Web browsers may give you different serious issues, may not even always report the problems in communication between you browser and the server, yada-yada-yada..
Yeah, but we want this functionality under the Web browser.
But what about using Java Web Start (JWS) to launch the full-fledged Swing clients? They can easily process events, work the same way under each operational system?
Yeah, but what if your users do not have the JVM?
But JWS can download it automatically for you.
Yeah, but what if you are Google, Amazon or EBay and want to have a very thin client.
OK, now we?re talking. I can agree that big Internet guys can and should invest some serious dough into supporting screen-refresh-on-mouse-move in HTML-based screens. But when it comes to a regular Intranet business application, when the users/browsers/platforms are known and when the cost of the project development matters, I?d stay with a fat client written in Java, or (if you like a fancy GUI) Macromedia?s Flash or Flex.
Read
Tutorial at: Click here to view the tutorial
Rate Tutorial: A cup of AJAX? Nay, just regular Java please
View Tutorial: A cup of AJAX? Nay, just regular Java please
Related
Tutorials:
|
Regular Expressions