1. Introducing the ToolTalk Service
2. An Overview of the ToolTalk Service
4. Setting Up and Maintaining the ToolTalk Processes
5. Maintaining Application Information
6. Maintaining Files and Objects Referenced in ToolTalk Messages
7. Participating in ToolTalk Sessions
Psignature Matching Information
Psignature Actions Information
Osignature Actions Information
Checking for Existing Process Types
13. Managing Information Storage
A. Migrating from the Classing Engine to the ToolTalk Types Database
B. A Simple Demonstration of How the ToolTalk Service Works
Since type information is only specified once (when your application is installed), your application needs to only declare its ptype each time it starts.
To declare your ptype, use tt_ptype_declare during your application's ToolTalk initialization routine. The ToolTalk service will create the message patterns listed in your ptype and any otypes that reference the specified ptype.
The message patterns created when you declare your ptype exist in memory until your application exits the ToolTalk session.
Note - The message patterns created when you declare your ptype information cannot be unregistered with tt_pattern_unregister; however, you can unregister these patterns with tt_ptype_undeclare.
The following listing illustrates how a ptype is registered during a program's initialization.
|