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
Identifying and Processing Messages Easily
Recognizing and Handling Replies Easily
Callbacks for Messages Addressed to Handlers
Attaching Callbacks to Static Patterns
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
When your process receives a request (class = TT_REQUEST), you must either reply to the request, or reject or fail the request.
When you reply to a request, you need to:
lists the ToolTalk functions you use to reply to requests.
Table 11-2 Functions to Reply to Requests
|
If you have examined the request and your application is not currently able to handle the request, you can use the ToolTalk functions listed in to reject or fail a request.
Table 11-3 Rejecting or Failing Requests
|
The return type for these requests is Tt_status.
If you have examined the request and your application is not currently able to perform the operation but another application might be able to do so, use tt_message_reject to reject the request.
When you reject a request, the ToolTalk service attempts to find another receiver to handle it. If the ToolTalk service cannot find a handler that is currently running, it examines the disposition attribute, and either queues the message or attempts to start applications with ptypes that contain the appropriate message pattern.
If you have examined the request and the requested operation cannot be performed by you or any other process with the same ptype as yours, use tt_message_fail to inform the ToolTalk service that the operation cannot be performed. The ToolTalk service will inform the sender that the request failed.
To inform the sender of the reason the request failed, use tt_message_status_set or tt_message_status_string_set before you call tt_message_fail.
Note - The status code you specify with tt_message_status_set must be greater than TT_ERR_LAST.