| Skip Navigation Links | |
| Exit Print View | |
|
ToolTalk User's Guide |
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
Including the ToolTalk API Header File
Registering with the ToolTalk Service
Registering in the Initial Session
Registering in a Specified Session
Registering in Multiple Sessions
Setting Up to Receive Messages
Sending and Receiving Messages in the Same Process
Unregistering from the ToolTalk Service
Using ToolTalk in a Multi-Threaded Environment
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
You can use the ToolTalk service in a networked environment; for example, you can start a tool on a different machine or join a session that is running on a different machine. To do so, invoke a ttsession with either the -c or -p option.
The -c option will invoke the named program and place the right session id in its TT_SESSION environment variable. For example, the command
ttsession -c dtterm
defines TT_SESSION in that cmdtool and any ToolTalk client you run with the environment variable $TT_SESSION set to its value will join the session owned by this ttsession.
The -p option prints the session id to standard output. ttsession then forks into the background to run that session.
To join the session, an application must either pass the session id to tt_default_session_set or place the session id in the environment variable TT_SESSION before it calls the tt_open function. tt_open will check the environment variable TT_SESSION and join the indicated session (if it has a value).
|