OpenSpeech Browser

Getting Started
Architecture Description
Integration Guide

Copyright (c) 1998-2001 SpeechWorks International, Inc. All Rights Reserved.


SBlog implementation of VXIlog
o SBlogStream
SBlog definition of a VXIlogStream
o SBlogErrorListener
Prototype for error listener notification
o SBlogDiagnosticListener
Prototype for diagnostic listener notification
o SBlogEventListener
Prototype for event listener notification
o SBlogContentListener
Prototype for content listener notification
o SBlog Interface
SBlog extension interface to the VXIlog interface.
o SBlogInit
Global platform initialization of SBlog
o SBlogShutDown
Global platform shutdown of Log
o SBlogCreateResource
Create a new log service handle
o SBlogDestroyResource
Destroy the interface and free internal resources
SBlog is an implementation of the VXIlog interface for logging. The SBlogInterface extends the VXIlogInterface to support a listener registration mechanism for sending the logs to the final output stream. This mechanism allows multiple systems to tap on to a single log event so it can be sent both to a file and to a central logging service is desired. Listeners are invoked through callbacks. The callback call is blocking. If a listener is going to do signficant work or invoke functions which may block, for example a socket write, a messsage queue should be implemented so that callback is non-blocking. Failure to do this will impact overall system performance.

Across all streams, SBlog is responsible for automatically supplying the following information for end consumer use:

In addition, for diagnostic logging the SBlog defines a mechanism for enabling/disabling messages on an individual tag basis without requiring a recompile for use by consumers of the diagnostic log. Diagnostic( ) is highly efficient for cases when the tag is disabled: in other words, the lookup for seeing if a tag (an integer) is enabled should be done using a simple array or some other extremely low-overhead mechanism. SBlog provides a way to enable/disable tags on-the-fly (without needing to restart the software).

Each OSB PIK component provides an XML error file which integrators can choose to us (or rewrite) to map error numbers and error key/values to error text. An XSLT transform can do this in an error viewer.

Alphabetic index Hierarchy of classes

This page was generated with the help of DOC++.