Before You Start

Before You Start

Before you start designing or coding your application, you need to plan for many issues that will affect its design and configuration. The following issues warrant particular attention.

Planning Issue

Description

Browser emulation

Determine what emulation mode your application must support. This can depend, for example, on whether your application will be rendering any accessible Web content or controlled and compliant content.

For more information, see Configuring the Browser Emulation Mode.

Protocol support

Determine if you require HTTP and HTTPS support.

If your application must support HTTP, authentication, caching, cookies, and proxies, you require the ICEhttp module.

If your application needs to support HTTPS, you need the optional ICEssl module.

If your application must authenticate to servers via the Microsoft NTLM authentication protocol, you need the optional ICEhttp NTLM module.

For more information, see Configuring Your Application to use HTTP or HTTPS.

GUI toolkit support

Determine what GUI toolkit your application will support.

For more information, see Configuring GUI Toolkit Support.

Content types

The content types your application needs to support affects your design, including what JAR files must be included.

For more information, see Pilots.

JavaScript support

Determine if JavaScript support is required for the content you wish to render.

For more information, see JavaScript.

Security

Security implementations in Java 1.1 and Java 2.0 vary considerably, and you must plan to enable security features accordingly.

For more information, see Security.

Accessibility

Your application can offer accessible features for users with disabilities with the optional Accessibility module. The Accessibility module provides support for both the Java Accessibility API and the industry-leading JAWS for Windows screen-reading software.

For more information, see Accessibility.

Deployment

Your application design may depend on how your application will be deployed, such as with Java Web Start, as a stand-alone application, or as a component within an enterprise application.

For more information, see Deployment Considerations.

Planning Issue	Description
Browser emulation	Determine what emulation mode your application must support. This can depend, for example, on whether your application will be rendering any accessible Web content or controlled and compliant content. For more information, see Configuring the Browser Emulation Mode.
Protocol support	Determine if you require HTTP and HTTPS support. If your application must support HTTP, authentication, caching, cookies, and proxies, you require the ICEhttp module. If your application needs to support HTTPS, you need the optional ICEssl module. If your application must authenticate to servers via the Microsoft NTLM authentication protocol, you need the optional ICEhttp NTLM module. For more information, see Configuring Your Application to use HTTP or HTTPS.
GUI toolkit support	Determine what GUI toolkit your application will support. For more information, see Configuring GUI Toolkit Support.
Content types	The content types your application needs to support affects your design, including what JAR files must be included. For more information, see Pilots.
JavaScript support	Determine if JavaScript support is required for the content you wish to render. For more information, see JavaScript.
Security	Security implementations in Java 1.1 and Java 2.0 vary considerably, and you must plan to enable security features accordingly. For more information, see Security.
Accessibility	Your application can offer accessible features for users with disabilities with the optional Accessibility module. The Accessibility module provides support for both the Java Accessibility API and the industry-leading JAWS for Windows screen-reading software. For more information, see Accessibility.
Deployment	Your application design may depend on how your application will be deployed, such as with Java Web Start, as a stand-alone application, or as a component within an enterprise application. For more information, see Deployment Considerations.