10.2.3.1 Advantages of a Multithreaded/Multicontexted ATMI Application

Multithreaded and multicontexted ATMI applications offer the following advantages:

• Improved performance and concurrency

  For certain applications, performance and concurrency can be improved by using multithreading and multicontexting together. In other applications, performance can be unaffected or even degraded by using multithreading and multicontexting together. How performance is affected depends on your application.

• Simplified coding of remote procedure calls and conversations

  In some applications it is easier to code different remote procedure calls and conversations in separate threads than to manage them from the same thread.

• Simultaneous access to multiple applications

  Your Oracle Tuxedo clients can be connected to more than one application at a time.

• Reduced number of required servers

  Because one server can dispatch multiple service threads, the number of servers to start for your application is reduced. This capability for multiple dispatched threads is especially useful for conversational servers, which otherwise must be dedicated to one client for the entire duration of a conversation.

For applications in which client threads are created by the Microsoft Internet Information Server API or the Netscape Enterprise Server interface (that is, the NSAPI), the use of multiple threads is essential if you want to obtain the full benefits afforded by these tools. This may be true of other tools, as well.