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 ToolTalk message server ttsession automatically starts when you open communication with the ToolTalk server. This background process must be running before any messages can be sent or received. Each message server defines a session.
To manually start a session, enter the following command on the command line:
ttsession [-a level][-d display][-spStvh][-{-E|X}][-c command]
See for a description of the ttsession command line options.
Table 2-1 ttsession Command Line Options
Note - If neither the -c, -d, or -p options are specified, ttsession starts an X session for the display specified in the $DISPLAY environment variable.
ttsession responds to two signals.
Run your application as its own session if it runs as a background job, in a batch session, or in a session bound to a character terminal. To run your application in its own session, use the -c parameter with the ttsession command, as follows:
ttsession -c [ command-to-non-in-batch ]
This command will fork off a shell from which you can run your application.
Note - The -c parameter must be the last option on the command line; any characters placed after the -c parameter on the command line are taken as the command to be executed.
To establish a session under the X Window System, execute ttsession either without arguments (which takes the display from the $DISPLAY environment variable) or specify the display with the -d parameter as follows:
ttsession -d :0
When ttsession is invoked, it immediately forks and the parent copy exits; the process managing the session executes in the background. The session is registered as a property, named by TT_SESSION on the root window of screen 0; the host and port number is given for communication with the process managing the session.
To display the sessid of the session for the Xdisplay:
xprop -root | grep TT_SESSION