When should I use a Java applet instead of AJAX?

Scenarios to use Java applet instead of AJAX:

• When there is a need for custom data streaming
• Need for graphic manipulation
• Threading related functionality
• Complex and advanced GUI manipulations.

• Applets provide features like custom data streaming, graphic manipulation, threading, and advanced GUIs which AJAX cannot.
• However, with the help of DHTML, the functionalities of AJAX can be extended further.
• AJAX requires that the browser be DHTML and AJAX capable.
• AJAX-based functionality does need to take browser differences into consideration due to which using a JavaScript library such as Dojo which abstracts browser differences is recommended.
• AJAX/DHTML works well for applications where the latest browsers are used.

How is encoding handled in AJAX?

Ways to handle encoding in AJAX:

• Using encodeActionURL() method to refresh the complete page
• Using encodeResourceURL() method to partially update a page.

Why is AJAX a comfortable fit with JAVA?

AJAX is a comfortable fit because, using Java Enterprise Edition the following tasks can be performed:

• AJAX client pages can be generated to server incoming AJAX requests
• Server side state is managed for AJAX clients
• AJAX clients can be connected to enterprise resources.