Browse Prior Art Database

Generalized Request/Reply Mechanism for Use in Asynchronous Distributed Environments

IP.com Disclosure Number: IPCOM000038358D
Original Publication Date: 1987-Jan-01
Included in the Prior Art Database: 2005-Jan-31
Document File: 7 page(s) / 25K

Publishing Venue

IBM

Related People

Cree, C: AUTHOR [+4]

Abstract

In today's office environment, effective management of time is one of the keys to personal productivity and success. For time management, people either use the telephone for confirming appointments or resort to paper calendars. However, they are not always at their desks, and the office system for an enterprise may include a variety of computer systems interconnected via phone lines and networks of different types. In order for individuals to schedule appointments, view calendars, or maintain calendars remotely between two remote nodes (just like the telephone), there is a need for a protocol to interchange information for time management between end users. A protocol is described that will facilitate communication between one or more end users in such an environment.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 18% of the total text.

Page 1 of 7

Generalized Request/Reply Mechanism for Use in Asynchronous Distributed Environments

In today's office environment, effective management of time is one of the keys to personal productivity and success. For time management, people either use the telephone for confirming appointments or resort to paper calendars. However, they are not always at their desks, and the office system for an enterprise may include a variety of computer systems interconnected via phone lines and networks of different types. In order for individuals to schedule appointments, view calendars, or maintain calendars remotely between two remote nodes (just like the telephone), there is a need for a protocol to interchange information for time management between end users. A protocol is described that will facilitate communication between one or more end users in such an environment. The command descriptions for Distributed Calendar Services (DCS) that permit Request/Reply Protocol for information interchange between end user nodes is described below. Two basic commands are described. 1. The REQUEST_ACTION command requests shipping of request(s) to one or more targets via an originating Office System Node

(OSN). 2. The ACTION_REPLY command requests shipping of a correlated reply for the recipient of the action requested by the

REQUEST_ACTION command to an OSN (in asynchronous

environment), or to the requestor in a point-to-point

environment, which then passes the reply back to the

originator of the REQUEST_ACTION command. This reply

may signify acceptance or rejection of the request with

or without a message related to the response. A detailed description of each command follows. The description begins with the command name and a list of the command operands. Optional operands are enclosed within brackets; required operands are shown without brackets. Operands are not repeatable unless explicitly stated in the command description. The function of the command is explained, followed by a description of each operand. the detailed operand definitions are contained in a subsection following command descriptions. The command structured fields (IDF) are defined in the subsequent section. Each command description contains the request/reply protocol used between the command requestor and command server. Normal and exception condition scenarios are shown. The command descriptions are concluded with a list of exception conditions which are specific to the command. The Distributed Calendar Services (DCS) pass information, such as requests to schedule appointments, request for updates to calendar, send response to a request, or send requests to view calendars, from requestor nodes to target nodes or OSNs within an office system network. The information flows can be between requesting and target nodes during a single (Document Interchange Architecture (DIA)) session, or by routing them through office system nodes for subsequent delivery to a target node. The Commands perform f...