| Skip Navigation Links | |
| Exit Print View | |
|
ToolTalk User's Guide |
1. Introducing the ToolTalk Service
Using the ToolTalk Desktop Services Message Set
Using the ToolTalk Document and Media Exchange Message Set
Integrating Multimedia Functionality
Adding Multimedia Extensions to Existing Applications
Extending the X Cut and Paste Facility
Using the CASE Interoperability Message Sets
Using the ToolTalk Filename Mapping Functions
Using ToolTalk in a Multi-Threaded Environment
How Applications Use ToolTalk Messages
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
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
Before you modify your application to use the ToolTalk service you must define (or locate) a ToolTalk message protocol: a set of ToolTalk messages that describe operations applications agree to perform. The message protocol specification includes the set of messages and how applications should behave when they receive the messages.
To use the ToolTalk service, an application calls ToolTalk functions from the ToolTalk application programming interface (API). The ToolTalk API provides functions to register with the ToolTalk service, to create message patterns, to send messages, to receive messages, to examine message information, and so on. To modify your application to use the ToolTalk service, you must first include the ToolTalk API header file in your program. You also need to modify your application to:
Initialize the ToolTalk service and join a session.
Register message patterns with the ToolTalk service.
Send and receive messages.
Unregister message patterns and leave your ToolTalk session.
|