On the client side, Java proves its viability with its ubiquitous availability on desktop and thin clients. In this article, Raghavan N. Srinivas introduces client-side deployment using several different Java technologies, with a particular focus on Java Web Start. (4,500 words)

The Java Web Start product includes a servlet in the developer's pack that can be used to package a JNLP file and its associated resources in a Web Archive (.war) file. The purpose of the servlet is to provide a simple and convenient packaging format for JNLP applications, so they can be easily deployment in a Web Container, such as Tomcat or a J2EE platform-compliant Application Server.
Table of Contents

• Introduction
• Examples
• Servlet Configuration
• Specifying Resources
• Mapping Requests to Resources
• Processing of JNLP Files

Browser-based user interfaces took us three steps forward in universal access, but two steps backward in usability. For customer-facing scenarios like eCommerce and internal scenarios like call centers, rich user interfaces can improve sales, reduce operational costs, and give time back to your knowledge workers. But a more effective information display is only the starting point for rich clients. Many user interface scenarios for both rich clients and browser-based applications benefit when they integrate content, workflow, collaboration, and local hardware resources, and when they coordinate across multiple interaction channels. To provide all of these capabilities in a unified way, interaction platforms are the long-term integrated answer. But they are not ready yet, so architects should use today's rich client products and technologies while keeping an eye on the future strategic platform picture.

Concentrant le meilleur des deux mondes, les clients riches remplaceront à terme les applications client-serveur traditionnelles. Les éditeurs se positionnent avec de nouvelles offres pour conquérir ce marché.