Rogue Wave banner
Previous fileTop of DocumentContentsIndexNext file

6.2 Execution Tracing Package Architecture

The Execution Tracing package consists of two parts, the trace macros and the trace classes. The trace macros include:

The trace classes include:

Only one client can connect directly to the trace manager. In cases where different categories of trace output must be treated differently, or some categories must be handled in multiple ways, a multi-client filter (splitter) is provided.

6.2.1 The Trace Output Pipeline

You can think of this pipeline for trace output as something equivalent to the flow of electrical current. The trace manager is like an electrical outlet that accepts only one plug. If you have a single appliance, you simply plug it in. If you have several appliances, you plug a power bar into the outlet and plug your appliances into the bar. In trace, a filter can work like a power bar when you need more than one client. For example, the application in Figure 27 uses a multi-client filter as a splitter, to log all the messages and also display the important ones on the screen.

Figure 27 -- Filtering trace events

You can chain any number of filters together in the pipeline, like the series of single-client filters in Figure 28. You could have each filter do one type of processing, for example.

Figure 28 -- Chaining trace event filters

6.2.2 Trace Class Hierarchy

Figure 29 shows the classes in the Execution Tracing package.

Figure 29 -- Trace class hierarchy


Previous fileTop of DocumentContentsIndexNext file

©Copyright 2000, Rogue Wave Software, Inc.
Contact Rogue Wave about documentation or support issues.