JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
ToolTalk User's Guide
search filter icon
search icon

Document Information

Preface

1.  Introducing the ToolTalk Service

2.  An Overview of the ToolTalk Service

3.  Message Patterns

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

8.  Sending Messages

9.  Dynamic Message Patterns

10.  Static Message Patterns

11.  Receiving Messages

12.  Objects

13.  Managing Information Storage

14.  Handling Errors

A.  Migrating from the Classing Engine to the ToolTalk Types Database

B.  A Simple Demonstration of How the ToolTalk Service Works

C.  The ToolTalk Standard Message Sets

The ToolTalk Desktop Services Message Set

Why the ToolTalk Desktop Services Message Set was Developed

Key Benefits of the ToolTalk Desktop Services Message Set

The ToolTalk Document and Media Exchange Message Set

ToolTalk Document and Media Exchange Message Set Development History

Key Benefits of the ToolTalk Document and Media Exchange Message Set

General ToolTalk Message Definitions and Conventions

Errors

General ToolTalk Development Guidelines and Conventions

Always Make Anonymous Requests

Let Tools Be Started as Needed

Reply When Operation has been Completed

Avoid Statefulness Whenever Possible

Declare One Process Type per Role

Developing ToolTalk Applications

Messaging Alliances

D.  Frequently Asked Questions

Glossary

Index

The ToolTalk Desktop Services Message Set

In order to achieve basic desktop integration, applications need to support a basic set of messages to enable inter-application control. The ToolTalk Desktop Services Message Set is the common message set that provides this functionality for all applications. A powerful messaging protocol that benefits both developers and users of desktop applications, the ToolTalk Desktop Services Message Set allows applications to easily interact with other desktop applications. Using the ToolTalk Desktop Services Message Set, applications can communicate with each other in a transparent manner, both locally and over networks.

Why the ToolTalk Desktop Services Message Set was Developed

In order to provide integrated control of applications, certain basic features are needed to launch, halt, control display appearance, and pass information regarding input and output data. All applications need to have these facilities so that other applications in the toolset can inter-change basic control information. This kind of functionality enables the development of smart desktops and integrated smart toolsets. Groups of applications can now call upon each other to perform tasks and to interact as one solution environment for the end-user.

Key Benefits of the ToolTalk Desktop Services Message Set

The ToolTalk Desktop Services Message Set offers developers two key benefits:

  1. Allows basic control of applications without direct intervention from the user. Routine or common procedures may be automated for the convenience of the user.

  2. Allows tool specialization through a common set of interactions. All ToolTalk aware applications can perform these functions.