Java Reference
In-Depth Information
N
OTE
It is important to realize that for some inexperienced End-Users, it is even hard to tell
the difference between the AH and the application itself. More generally, designers
and programmers should always keep the typical client-side launching scenario in
mind. A common bad design hint is the long sequence of different splash screens
(first the AH; then the application start-up; then the application Web connection back
to server data) proposed to the end-user by some AH-launched applications. (For an
example, see Chapter 7, “Building Your Own Deployment Solution.”)
2
Figure 2.8 illustrates the whole deployment process, as perceived by the End-User. The num-
bers next to arrows describe the sequence of execution steps from the user's perspective.
Installation
Entry Point
Tr ansfer Time
2
AH Interaction
End-User
3
Application
(Java
Env.)
AH Launch time
1
AH
Client Environment
HW + OS
F
IGURE
2.8
End-User perceived complexities in the deployment process.
An unskilled End-User is aware only of those parts of the process that are
visible
to her or him.
Let's examine the main points of End-User interaction with our deployment model.
1.
Entry Point Complexity
The complexity of the sequence of actions the End-User has to
carry out to launch the whole deployment process. Often automatically deployed applica-
tions are somehow hidden from the End-User's access, so this factor is negligible, espe-
cially for inexperienced End-Users.
2.
AH Launch Time
Often can include the transfer time as well.
