Deploying Existing Software - Java Deployment with JNLP and WebStart - page 140

T ABLE 6.1. Continued
Deploy- Java Needed Deploy- User Deve- Needed Installed Code

ment Edition Connection ment Costs loper Server Appl. Adaptation

Solution Features Costs Support Richness

Personnel Any None High Low High None High Low

Third- Any Various High Low MediumVarious High Low

Party
Solutions
Applets Java 1 HTTP Basic Low Low Low Low High

Applets J2SE HTTP Basic High Low Low Medium High

with
Plug-In

In this table, the major choices are compared using imprecise evaluation parameters. The aim
is to provide an initial, intuitive overview of the tradeoffs implied in the available deployment
solutions.

The parameters considered are as follows:

• Deployment Solution . One of the major deployment techniques discussed above. The
ad-hoc option has not been considered because of its excessive generality.
• Java Edition . It may have two values: Java 1 (intending JDK 1.x) and J2SE. We
restricted our discussion to the J2SE only in this chapter.
• Needed Connection . The kind of connection required by the chosen deployment solu-
tion.
• Deployment Features . The level of features supported by the given deployment solution
(refer to Chapter 4).
• User Costs . The burden posed to the end-user (considered not familiar with computers
programs).
• Developer Costs . The development (and the subsequent deployment) effort in license
fees, workforce wages, and other costs.
• Needed Server Support . The minimum server support required. This can be thought of
as a part of the overall deployment costs. Low is intended for a basic web server. Third-
party solutions vary greatly in this parameter.
• Installed Application Richness . How powerful the installed application could be. This
column is significant only for applets.
• Code Adaptation . The last column shows how that given solution is combined with
already written Java code. For example, although installation packagers work well with