Jolt 1.2 Developer's Guide

Note
Sun has indicated that JDK 1.1 will implement preemptive threads, and should alleviate the requirement for yields. Code that
includes yields will continue to work; code without yields will begin working with the JDK 1.1 release.
Using Threads for Asynchronous Behavior
You can use threads in Jolt to get asynchronous behavior that is analogous to the tpcall() function in NonStop
TM
TUXEDO. With this capability,
you do not need a asynchronous service request function. You can get this functionality because Jolt is thread safe. For example the client Jolt
application can start one thread that sends a request to a NonStop
TM
TUXEDO service function and then immediately starts another thread that
sends another request to a NonStop
TM
TUXEDO service function. So even though the Jolt tpcall() is synchronous, the application is asynchronous
because the two threads are running at the same time.
Using Threads with Jolt
A Jolt client-side program or applet is fully thread-safe. Jolt's support of multi-threaded applications includes the following client characteristics:
Multiple sessions per client●
Multithreaded within a session●
Client application manages threads, not asynchronous calls●
Performs synchronous calls●
The following program illustrates the use of two threads in a Jolt application.
Example 6-10. Using Multithreads with Jolt (ThreadBank.java)