CORBA 2.6.1 Glossary

thread is suspended or destroyed.
Threads differ from server pools in that threads require the same process to handle multiple
requests, whereas server pools allow requests to be handled by different processes running in
parallel.
thread-blocking operation
Operations that block only the calling thread, rather than the entire process, while they are in
progress. Examples are nowait file I/O operations and operations directed to distributed objects.
thread-safe code
Code in a multithreaded program that protects an object from access by more than one thread at a
time. Mechanisms to provide thread-safe code include mutexes in C++ and monitors in Java.
three-tiered architecture
See tiered application architecture.
tiered application architecture
An application model in which function is divided into a few major categories of objects, such as
interface, control, and entity objects.
TMF
See Transaction Management Facility (TMF).
trace
A sequential record of data or program flow, useful for troubleshooting. NonStop CORBA
includes facilities to trace the flow of control within an application.
trace facility
An object API that writes trace messages to an ASCII file. The trace facility can be used to
implement instrumentation in NonStop CORBA applications. You can add trace statements to
specific portions of NonStop CORBA applications or components to help troubleshoot program
code.
transaction
A series of logically related operations. A transaction is complete only when all operations in the
series have been performed. This manual makes a distinction between user or application
transactions, which are defined and controlled by application components, and services
transactions, which are defined and controlled by objects services such as the Naming Service.
transaction management
A set of tasks required to ensure satisfactory transaction processing. Transaction management
includes transaction control (the application logic that determines when a transaction starts and
stops, and when and how to abort a transaction), transaction protection, and auditing (logging the
progress of transactions to support request tracking and recovery). A NonStop CORBA application
controls transactions by using the Object Transaction Service (OTS).