Oracle Solaris 8 CDE：ToolTalk消息系统概览

需积分: 5 90 浏览量更新于2024-06-24 收藏 259KB PDF 举报

Oracle Solaris 8 Common Desktop Environment (CDE) 是一个基于Sun Microsystems（现已被Oracle收购）的操作系统环境，专注于提供企业级桌面管理与协作功能。CDE是Solaris平台上的一个重要组成部分，它为用户提供了一个统一、稳定且高效的桌面体验，特别强调了工具集成和通信能力。其中提到的"ToolTalk Messaging" 是CDE中的一个重要组件，它是一种消息传递服务，允许不同应用程序和服务之间无缝通信。在Oracle Solaris 8的CDE架构中，ToolTalk Messaging负责实现用户之间的即时通讯，比如消息通知、文件传输和协作工作流程，这些都是现代办公环境中不可或缺的功能。它通过标准的接口和协议，如Internet Protocol (IP) 和简单网络管理协议(SNMP)，支持多种网络环境下的消息传递。该文档详细介绍了如何在Solaris 8环境中配置、管理和维护ToolTalk Messaging服务，包括安装步骤、安全设置、性能优化以及故障排查方法。此外，文档还强调了版权问题，指出所有产品或文档的使用都受到严格的限制，必须获得Sun Microsystems及其供应商的书面授权，确保遵循版权法和许可证条款。对于第三方软件的使用，如字体技术，通常会涉及到多个供应商的许可协议。Oracle Solaris 8 CDE中可能包含了来自Berkeley BSD系统的部分代码，并且在某些情况下，Unix是经过X/Open Company Ltd.独家许可的注册商标。在Sun Microsystems的商标策略中，"Sun"、"Sun Microsystems"、"docs.sun.com"、"AnswerBook"、"AnswerBook2"以及"Solaris"等都是其在美国和其他国家享有权利的商标或服务标志。此外，SPARC是专用于Sun特定处理器架构的商标。 Oracle Solaris 8 Common Desktop Environment的ToolTalk Messaging部分提供了企业级用户的实时通信解决方案，它与操作系统紧密结合，增强了系统的易用性和协作效率。同时，用户在享受这些功能时，需要严格遵守版权和许可规定，确保合法使用。

What Kind of Work Problems Can the

ToolTalk Service Solve?

This section describes some of the inter-operability problems the ToolTalk service is

designed to solve. The ToolTalk service is the appropriate technology to use if your

application needs:

Tool inter-changeability

Control integration

Network-transparent events that are not owned by any well-known server (for

example, an X server) and that do not have any predictable set of listeners

Automatic tool invocation

A widely-available distributed object system

Persistent objects

Of course, there are some inter-operability problems for which the ToolTalk service

may not be the appropriate technology to use. However, when your application

needs to solve both sorts of problems (that is, a combination of those

inter-operability problems for which the ToolTalk service is designed to solve and

those problems for which it is not designed), you can use the ToolTalk service in

combination with other technologies.

Tool Interchangeability

Use the ToolTalk service when you want plug-and-play capability. The term

plug-and-play means that any tool can be replaced by any other tool that follows the

same protocol. That is, any tool that follows a given ToolTalk protocol can be placed

(plugged) into your computing environment and perform (play) those functions

indicated by the protocol. Tools can be mixed and matched, without modiﬁcation

and without having any speciﬁc built-in knowledge of each other.

Control Integration

Use the ToolTalk service when your application requires control integration. The

term control integration indicates a group of tools working together toward a common

end without direct user intervention. The ToolTalk service enables control integration

through its easy and ﬂexible facilities for issuing arbitrary requests, either to speciﬁc

tool instances or to anonymous service providers.

Common Desktop Environment: ToolTalk Messaging Overview ♦ February 2000

Scenarios Illustrating How the ToolTalk Service

Helps Solve Work Problems

The scenarios in this section illustrate how the ToolTalk service helps users solve

their work problems. The message protocols used in these scenarios are hypothetical.

Using the ToolTalk Desktop Services Message Set

The ToolTalk Desktop Services Message Set allows an application to integrate and

control other applications without user intervention. This section presents two

scenarios (“The Smart Desktop” on page 18 and “Integrated Toolsets” on page 19)

that show how the Desktop Services Message Set might be implemented.

The Smart Desktop

Note - The scenario in this section is intended to illustrate how the ToolTalk service

can be used in an application-level program that interprets user requests; it is not

intended to illustrate how the Common Desktop Environment product implements

the ToolTalk service to interpret user requests.

A common user requirement for a graphic user interface (GUI) front-end is the

ability to have data ﬁles be aware (or “know”) of their applications. To do this, an

application-level program is needed to interpret the user’s requests. Examples of

application-level programs (known as smart desktops) are the Apple Macintosh ﬁnder,

Microsoft Windows File Manager, and the Common Desktop Desktop File Manager.

The key common requirements for smart desktops are:

1. Takes a ﬁle

2. Determines its application

3. Invokes the application

The ToolTalk Service provides additional ﬂexibility by allowing classes of tools to

edit a speciﬁc data type. The following scenario illustrates how the Desktop Services

Message Set might be implemented as a smart desktop transparent to the end-user.

1. Diane double-clicks on the File Manager icon.

The File Manager opens and displays the ﬁles in Diane’s current directory.

2. Diane double-clicks on an icon for a data ﬁle.

a. The File Manager requests that the ﬁle represented by the icon be

displayed. The File Manager encodes the ﬁle type in the display

message.

b. The ToolTalk session manager matches the pattern in the display

message to a registered application (in this case, the Icon Editor),

Common Desktop Environment: ToolTalk Messaging Overview ♦ February 2000

and ﬁnds an instance of the application running on Diane’s

desktop.

Note - If the ToolTalk session manager does not ﬁnd a running

instance of the application, it checks the statically-deﬁned process

types (ptypes) and starts an application that best matches the

pattern in the message. If none of the ptypes matches, the session

manager returns failure to the File Manager application.

c. The Icon Editor accepts the display message, de-iconiﬁes itself, and

raises itself to the top of the display.

3. Diane manually edits the ﬁle.

Integrated Toolsets

Another signiﬁcant application for which the Desktop Services Message Set can be

implemented is integrated toolsets. These environments can be applied in vertical

applications (such as a CASE developer toolset) or in horizontal environments (such

as compound documents). Common to both of these applications is the premise that

the overall solution is built from specialized applications designed to perform one

particular task well. Examples of integrated toolset applications are text editors,

drawing packages, video or audio display tools, compiler front-ends, and debuggers.

The integrated toolset environment requires applications to interact by calling on each

other to handle user requests. For example, to display video, an editor calls a video

display program; or to check a block of completed code, an editor calls a compiler.

The following scenario shows how the Desktop Services Message Set might be

implemented as an integrated toolset:

1. Bruce is working on a compound document using his favorite editor.

He decides to change the some of the source code text.

2. Bruce double-clicks on the source code text.

a. The Document Editor ﬁrst determines the text represents source

code and then determines which ﬁle contains the source code.

b. The Document Editor sends an edit message request, using the ﬁle

name as a parameter for the message.

c. The ToolTalk session manager matches the pattern in the edit

message to a registered application (in this case, the Source Code

Editor), and ﬁnds an instance of the application running on

Bruce’s desktop.

Introducing the ToolTalk Service 19

剩余127页未读，继续阅读

weixin_40191861_zj

粉丝: 83
资源: 1万+

Oracle Solaris 8 CDE：ToolTalk消息系统概览

Oracle Solaris 9 Common Desktop Environment: Product Glossary-10

Oracle Solaris 8 Solaris Common Desktop Environment: User’s Guid

Oracle Solaris 8 ToolTalk User’s Guide-247

Oracle Solaris 9 ToolTalk User’s Guide-238

Oracle Solaris 10 ToolTalk User's Guide-220

CIS_Solaris_10_Benchmark_v5.0.0

Solaris操作系统用户全面指南

Sun Solaris公用桌面环境用户指南

AIX 5.3/6.1堆溢出新利用机制：原理与实证

目标检测数据集：瓶子图像缺陷检测数据【VOC标注格式】

最新资源