To understand what AJAX applications are, see http://en.wikipedia.org/wiki/AJAX for a generic description. 

Benefits of AJAX applications

See http://en.wikipedia.org/wiki/AJAX for a general description of the benefits of an AJAX application.

In the Framework, AJAX applications offer:

• Optimal web performance by avoiding full page or full frame refreshes.
• The ability to create web forms that are close to Windows rich client in function and speed..
• On-the-fly data validation.
• On-the-fly data fetching/updating/deleting.
• Maximum control and freedom in processing logic and UI interactions.

Disadvantages of AJAX applications

Compared to WAM applications, AJAX application development requires an extended skill set and usually longer development times.

Also, AJAX applications generally produce higher web and application server hit rates. The requests are usually simpler but made more often. This changes the profile of the performance load on your web and application servers. This is a very important consideration in your application design.   

When should I use an AJAX application?

Generally, you should only use  AJAX applications when the additional cost of developing them is less than the value of the benefit they deliver (the problem of course is in assessing the true value of the benefit they deliver).     

A typical Framework-WEB application should mainly consist of WAM functions, with the occasional AJAX routine used in selected application areas.

You might use AJAX:

• When optimal performance is required (for example high volume data entry).
• When optimal or elaborate UI interactions are required (for example order entry).
• As demonstration vehicles for customer or end-users.
• In areas that are very heavily used by customer or end-users.
  
  

See also

• Mandatory Skills
• AJAX Applications in the Framework
• AJAX Exercises
• Tracing
• Messages and Errors
• Frequently Asked Questions
• Restrictions
• Recommendations