Developing lightweight J2EE client applications that interoperate with
multiple application servers can be difficult to do. Having to include an
application server-specific JAR file along with a thin client application can
significantly increase the size of the deployed application and make it too
big to be practical.
In addition, client-side execution is tightly coupled using proprietary
app-server extensions. This is especially true when mixing and matching
multiple J2EE vendors together (such as a Tomcat servlet container
communicating with a WebLogic EJB tier). Standard prot... (more)
Caching information on the WebLogic tier can significantly increase
performance and reduce the number of external system calls needed for data
retrieval. This is especially true when an application wants to store bits of
information that rarely change, such as a list of countries or catalog
entries. Nowadays, memory is so cheap that application architectures can
benefit from caching data... (more)
The advent of AJAX as a Web application model is significantly changing the
traffic profile seen on the server side. The typical Web pattern usage of a
user sitting idle on a Web page filling out fields and hitting the submit
button to the next link is now transforming into sophisticated client-side
JavaScript and rich user interfaces that constantly communicate with the
server whenever ... (more)
The advent of AJAX as a Web application model is significantly changing the
traffic profile seen on the server side. The typical Web pattern usage of a
user sitting idle on a Web page filling out fields and hitting the submit
button to the next link is now transforming into sophisticated client-side
JavaScript and rich user interfaces that constantly communicate with the
server whenever ... (more)