-
Extremely rapid loading of Java applications
under a single Java Virtual Machine (JVM)
-
Greatly reduced impact on system resources,
such as memory consumption and the number of system threads
or processes allocated to execute the applications
-
Users are not forced to use FastPak for
starting all current Java applications since it does not take
over a system.
-
Applications may be run as Java archive (jar)
files, as well as un-jarred (flat) applications on the end
users machines
-
FastPak can automatically launch applications
specified to do so in their application profiles when FastPak
is started
-
Applications in a Java archive format can be
launched remotely if hosted on a web server within a secure
network
-
FastPak does not interfere with any network
connections an application attempts to make unless an
application imposes a security manager that prevents such
access
-
Users can easily configure new applications
to be run under FastPak via a graphical user interface that
is easy to understand and easy to use.
-
Several instances of a given application can
be run with differing command line (input) parameters in
complete isolation from one another provided they adhere to
FastPak's design guidelines.
-
The FastPak GUI user interface can be used to
override existing input parameters for a given application
without permanently modifying the configuration parameters of
the application.
-
A very simple API and associated libraries
are provided which allow developers to do such things as
create custom graphical user interfaces for running and
controlling FastPak, launch applications from one machine on
another machine, and obtain information about FastPak locally
and remotely via FastPak's Controller Thread
-
Application priorities can be set during
application configuration thus allowing users to control
which applications may use higher or lower levels of CPU with
respect to one another
-
Displays logging data regarding the status of
applications, threads, configuration, etc. This logging
information may be stored on disk continuously or sections of
it displayed by the FastPak graphical user interface may be
highlighted and saved to a separate file for analysis, with
comments if desired.
-
A daemon mode and limited command line
console are available via configuration, hence allowing
FastPak to be run without a graphical user interface.
-
Provides a tool (TranferUtility.jar) to
assist in distributing configured applications to other users
machines.
-
FastPak comes with a set of pre-configured
applications which illustrate how to set up FastPak for both
jar and flat applications, as well as remote jar based
applications.
-
The FastPak graphical user interfaces
incorporates an HTML based help system that is detailed and
accurate.
-
FastPak can support JNI based applications
provided they don't redundantly load native libraries.
-
FastPak can bring life back to older, slower
hardware since such machines may be heavily taxed by
application launching with discrete JVMs.
