JADE Thin Client Restrictions

When you run JADE as a presentation client:

• Event methods that are added to a JADE application are not invoked for a form that is running, until that form is restarted.

• Control class event methods that are added are not invoked until the application is restarted.

• Do not use the bufferAddress method of the String or Binary primitive type when your application is running in JADE thin client mode, as the use of this method may corrupt your machine as you are passing an address relating to one machine to another machine.

• An external method call made from JADE logic executes on the application server workstation and not that of the presentation client.

• Shared transient instances are shared among all presentation clients connected to the same application server. Logic obtaining the first shared transient instance of a class may therefore no longer work as expected.

• Use of timers whose logic interacts with the presentation client side of the thin client processing may cause a processing loop if the interval between timer calls is less than the time taken to process each request. This could arise over a slower-speed line where the transmission time to the presentation client becomes significant.

  When you develop an application that could run in JADE thin client mode, use timers with care. When a timer event occurs, it notifies the application server, which then echoes the event to all attached presentation clients (that is, the application server sends the notification to each presentation client, which then send a response to the application server). This can have a considerable impact on network traffic.

• Locale handling uses the locale id that is in use on the presentation client workstation, by default. This locale must be installed on the application server workstation. Any local changes on the presentation client to the locale options are ignored (for example, the date format). As inconsistent results could be returned to the application server when there are regional overrides on presentation clients, all overrides on the application server are suppressed by default. For more details, see "JADE Functionality Affected by Thin Client Operation", earlier in this appendix.

  The locale of the presentation client is used to determine the locale to run the thread for that client on the application server machine. It then uses the regional settings of the application server for that locale to determine the formatting of any locale-specific dates, times, and so on. You therefore cannot customize the results returned from a shortFormat method or any locale-dependent method on a presentation client. Set the EnhancedLocaleSupport parameter in the [JadeEnvironment] section of the JADE initialization file to true if you want regional overrides set on the presentation client to be forwarded to the application server so that both use consistent locale settings for the application.

• It is assumed that any fonts set by logic are available on both the application server and the presentation client workstation. When the font setting of the application server matches that of the presentation client workstation (for example, both use small fonts), some font-sizing requests are performed on the application server

• To minimize the footprint of the Presentation Client installation type, the online help files and their required support binaries are neither installed nor shipped for that type of installation.

  If users in JADE thin client mode require JADE online help, install the presentation client software, and then separately use the Custom installation option of the full installation CD-ROM and check the On-line Help Files component in the Select Components dialog.