Apple WebObjects 5 - Manual (Page 94)

94 Combining Approaches

Apple Computer, Inc. January 2002
C H A P T E R 8
Choosing Your Approach
applications as well. For internal applications, the user interface polish is not as
important as development time, making these applications ideal candidates for
the WebObjects rapid development approaches.
Combining Approaches
WebObjects does not confine you to a single approach. You can switch your
approach as you develop your application or combine it with another approach.
This is possible in WebObjects because the business logic is encapsulated in
enterprise objects and not in the application.
Combining HTML-based and Java Client
Approaches
In general, you shouldn’t combine a HTML-based approach (WebObjects
HTML-based or Direct to Web) with a Java Client approach (Java Client or Direct to
Java Client) because the combination has none of the advantages and all of the
drawbacks of the individual approaches. The speed and interactivity of their user
interfaces are major advantages of Java Client applications. These advantage are
lost when the applications also use inherently less-interactive HTML-based
interfaces.
Similarly, a major advantage of HTML-based applications is that any computer
with a Web browser can use them. When combined with Java Client, these
applications depend on the quality of the browser’s Java Virtual Machine, if the
browser even implements one. In addition, you must install the client code on the
user’s computer or force the user to wait for it to download. The extra interactivity
Java Client adds to the HTML-based approaches is usually outweighed by the
concomitant loss of portability.