Ad-Hoc Deployment Services
JNLP 1.0 Deployment
“One shot” Deployment
F IGURE 7.1
Choosing the deployment implementation starting point.
Such trade-offs are typical of the design of custom deployment solutions. Often, the best way
is to customize an existing deployment solution, rather than building one totally from scratch.
This choice needs experienced developers with that given technology and a clear view of the
available design choices. What was said in Chapter 4 about general deployment design applies
here as well.
To recap, when we need to implement an ad-hoc deployment circuit, we have to decide which
deployment means (among one of those defined in Chapter 4) is best suited for implementing
the base of our deployment circuit. In making this decision, we should consider the parameters
used for customizing standard deployment technologies (license fees, end-user impact, etc.; see
Chapter 4) plus our ability to effectively provide ad-hoc code built on top of the chosen
deployment technology in order to implement the planned services. This latter aspect may
involve considerations such as the level of experience with the given technology, time to mar-
ket, and other useful software development figures.