| Skip Navigation Links | |
| Exit Print View | |
|
ToolTalk User's Guide |
1. Introducing the ToolTalk Service
2. An Overview of the ToolTalk Service
Maintaining ToolTalk Files and Databases
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 following ToolTalk service components work together to provide inter-application communication and object information management:
ttsession is the ToolTalk communication process.
This process joins together senders and receivers that are either using the same X server or interested in the same file. One ttsession communicates with other ttsessions when a message needs to be delivered to an application in another session.
rpc.ttdbserverd is the ToolTalk database server process.
One rpc.ttdbserverd is installed on each machine which contains a disk partition that stores files of interest to ToolTalk clients or files that contain ToolTalk objects.
File and ToolTalk object information is stored in a records database managed by rpc.ttdbserverd.
libtt is the ToolTalk application programming interface (API) library.
Applications include the API library in their program and call the ToolTalk functions in the library.
The ToolTalk service uses the Remote Procedure Call (RPC) to communicate between these ToolTalk components.
Applications provide the ToolTalk service with process and object type information. This information is stored in an XDR format file, which is referred to as the ToolTalk Types Database in this manual.
|