Apple WebObjects 5 - Manual (Page 92)

92 User Interface Requirements

Apple Computer, Inc. January 2002
C H A P T E R 8
Choosing Your Approach
Java Client and Direct to Java Client applications are generally unsuitable for public
websites because they contain client code that runs on the user’s computer. Not only
must the user wait for this code to download, but also the quality of the user’s Java
Virtual Machine determines whether the application runs correctly, efficiently, and
attractively.
User Interface Requirements
The WebObjects development approaches differ in the richness and response times
of the user interfaces and the ease in which you can make user interfaces with
specific layout and flow requirements.
Rich Widget Selection and Fast Response Times
The Java Client and Direct to Java Client approaches offer user interfaces with
multiple windows and a large selection of widgets, features commonly found in
client-server applications. If your application needs these features, you should use
one of these approaches. The HTML user interface used by the WebObjects
HTML-based and Direct to Web approaches offers much more limited possibilities.
When you need fast response times from your user interface (if you’re displaying
and updating real time data, for example), you should use the Java Client or Direct
to Java Client approaches. The user’s computer manages the highly interactive user
interface.
The drawback of the Java Client approaches is you need to be sure the client code is
on the user’s computer when the user runs your application. You can either install
it on the user’s computer in advance like a standalone application, which can be
inconvenient, or download it as an applet, which can take a long time.
Specific Layout and Flow Requirements
If you plan to create an HTML application with specific page design and flow
requirements, you should use the WebObjects HTML approach. The alternative,
Direct to Web, creates applications with a predefined structure that limits the user