1. Introducing the ToolTalk Service
2. An Overview of the ToolTalk Service
Scoping to a File in a Session
Scoping to a File and/or a Session
Adding Files to Scoped Patterns
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
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
The attributes in your message pattern specify the type of messages you want to receive. Although some attributes are set and have only one value, you can supply multiple values for most of the attributes you add to a pattern.
provides a complete list of attributes you can put in your message patterns.
Table 3-1 ToolTalk Message Pattern Attributes
|
All your message patterns must at least specify:
Category — Whether the application wants to perform operations listed in messages or only view messages.
Use TT_OBSERVE if you only want to observe messages.
Use TT_HANDLE if you want to perform operations requested by the messages.
Use TT_HANDLE_PUSH if you want to use the most recently registered pattern of this category (if any) before using any pattern of another HANDLE category
Use TT_HANDLE_ROTATE if you want to use TT_HANDLE. If no eligible TT_HANDLE_PUSH patterns are found, use the TT_HANDLE_ROTATE pattern that was least recently used to deliver a message before using any TT_HANDLE patterns.
Scope — Whether the application is interested in messages about a particular session or file.
Use TT_SESSION to receive messages from other processes in your session.
Use TT_FILE to receive messages about the file you have joined.
Use TT_FILE_IN_SESSION to receive messages for the file you have joined while in this session.
Use TT_BOTH to receive both messages for the file, the session, or the file and the session you have joined.
The ToolTalk service compares message attributes to pattern attributes as follows:
The ToolTalk service counts the message attribute as matched if:
No pattern attribute is specified.
The pattern does not name a context slot.
The pattern has an empty context slot.
Note - The fewer pattern attributes you specify, the more messages you become eligible to receive.
If there are multiple values specified for a pattern attribute, one of the values must match the message attribute value. If no value matches, the ToolTalk service will not consider your application as a receiver.
If context slots are contained in the message, the ToolTalk service will not consider your application as a receiver unless:
A value specified in a context slot of a pattern matches the value specified in the message context slot.
When multiple context slots are specified in a message, each context slot value in the message matches a corresponding context slot value in the pattern.