Later, I'll demonstrate the benefits of AJAX using a test case application for a chemical sales company
Tutorial Details:
The application was built with ASP.NET (C#) and SQL Server, and worked by triangulating medical providers out of a database near a specific address. Customers could pick from a list of search options and build queries like "I'd like to find cardiologists within 15 miles of 01824" or "I'd like to find cardiologists within 15 miles of 01824 that have practiced medicine for at least 13 years and graduated from XYZ College", etc… Any time customers would refine their search options, my code would locate medical providers and update a list in their browser.
The problem with this application is that it was slow and not very responsive. When a customer would select more specific search options, the request was routed to the server, the database would go through the triangulation algorithm, and eventually the list of medical providers would get displayed in the user's browser. Often times, a complex query could take over a minute to complete.
Furthermore, when our company would sign a contract with an employer they would pick a specific day to customize medical insurance plans with their employees. This meant that many employees would configure their healthcare options at the same time. Considering that our application was running on only one server, and we only had one database server, this would generally cause our application to slow down exponentially. Sometimes, this bottleneck would cause our application to crash or would cause our customer's requests to time-out.
This is where AJAX would have been useful. AJAX is an acronym for Asynchronous JavaScript and XML and is a technology for using client-side JavaScript to interact with a Web Server to manage Data and User Interface. The idea is to move some of the processing within a web application from the server, to the client.
Today, the average home PC comes standard with 512 Mb of RAM, and a 3 GHz CPU. Clearly, you can see the benefit to taking advantage of that client-side processing power in building our web applications. This is possible because most of today's web browsers are capable of using JavaScript (ECMAScript) and more importantly, XML.
Read
Tutorial at: Click here to view the tutorial
Rate Tutorial: AJAX Isn't All Purpose Soap
View Tutorial: AJAX Isn't All Purpose Soap
Related
Tutorials:
 Clean up your wire protocol with SOAP, Part 1 - JavaWorld March 2001
Clean up your wire protocol with SOAP, Part 1 - JavaWorld March 2001
|
Clean up your wire protocol with SOAP, Part 2 - JavaWorld April 2001
Clean up your wire protocol with SOAP, Part 2 - JavaWorld April 2001
|
Clean up your wire protocol with SOAP, Part 3 - JavaWorld June
2001
Clean up your wire protocol with SOAP, Part 3 - JavaWorld June
2001
|
XML messaging, Part 2 - JavaWorld June
2001
XML messaging, Part 2 - JavaWorld June
2001
|
Clean up your wire protocol with SOAP, Part 4 - JavaWorld July
2001
Clean up your wire protocol with SOAP, Part 4 - JavaWorld July
2001
|
XML messaging, Part
3
XML messaging, Part
3
|
Axis: The next generation of Apache SOAP
Axis: The next generation of Apache SOAP
|
Cache SOAP services on
the client side
Cache SOAP services on
the client side
|
Jtrix: Web
services beyond SOAP
Jtrix: Web
services beyond SOAP
|
Discover and publish Web services with JAXR
Discover and publish Web services with JAXR
|
Yes, you can secure your Web services documents, Part 2
Yes, you can secure your Web services documents, Part 2
|
Publish and find UDDI tModels with JAXR and
WSDL
Publish and find UDDI tModels with JAXR and
WSDL
|
Axis-orizing objects for SOAP
Axis-orizing objects for SOAP
|
SAAJ: No strings attached
SAAJ: No strings attached
|
Call on extensible RMI
Call on extensible RMI
|
2Way HTTP Compression Servlet Filter
2Way HTTP Compression Servlet Filter
2Way compression filter is a Servlet filter that compresses and decompresses both HTTP requests and HTTP responses using gzip. It was originally written to compress SOAP messages, but it can be used for any Web appl
|
Free SOAP Monitor
Membrane SOAP Monitor is a free Web Services development tool for inspecting and manipulating SOAP messages. It acts as a SOAP proxy between a consumer and a producer. SOAP messages can be intercepted, viewed and modified.
|
Leverage JNLP and SOAP for Java Thick-client Development
Leverage JNLP and SOAP for Java Thick-client Development
The hype during the mid-to-late 1990's over Java's utility to run swarms of autonomous applets was greatly exaggerated. This early enthusiasm (and marketing) for Java as a language with which devel
|
Streaming QuickTime with Java
This isn't an excerpt from my soon-to-be-released QuickTime for Java book, though now I wish it was.
|
Comparing J2ME Multimedia Options
This article presents the latest developments in MMAPI: the new security considerations raised in MMAPI 1.1, the differences between MMAPI and the MIDP 2.0 Media API, J2ME Wireless Toolkit 2.2 support for MMAPI, and JSR 234, Advanced Multimedia Supplement
|
|
|
|
