Browse Prior Art Database

Generalized Process Network Server

IP.com Disclosure Number: IPCOM000040343D
Original Publication Date: 1987-Oct-01
Included in the Prior Art Database: 2005-Feb-02
Document File: 1 page(s) / 11K

Publishing Venue

IBM

Related People

Cree, CM: AUTHOR [+4]

Abstract

A method is described for generalizing the interface to a variety of computer systems interconnected by networks of different types. This capability is provided by using a generalized server that can process requests between end users in a network. In the past many of the computer systems could not exchange information due to unresolved interfaces. The disclosed method uses a command processor which examines the header of each transaction sent to the server. A value contained in the header is looked up in a process-server table to determine if the application can be immediately accessed. If the application is available, the transaction is sent to the application. If the application is unavailable, it is added to a queue of requests and processed first-in, first-out.

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

Page 1 of 1

Generalized Process Network Server

A method is described for generalizing the interface to a variety of computer systems interconnected by networks of different types. This capability is provided by using a generalized server that can process requests between end users in a network. In the past many of the computer systems could not exchange information due to unresolved interfaces. The disclosed method uses a command processor which examines the header of each transaction sent to the server. A value contained in the header is looked up in a process-server table to determine if the application can be immediately accessed. If the application is available, the transaction is sent to the application. If the application is unavailable, it is added to a queue of requests and processed first-in, first-out. The application returns a code which indicates whether the request should be enqueued to the addressed user or not. If it is not to be enqueued, the control processor discards the transaction; otherwise, the transaction from the application is routed back to the original requestor application. Using the described interface, applications from diverse systems can communicate intelligently and exchange information. Such functions as calendaring, distributing messages, updating host support information, scheduling group appointments, listing queued requests, and finding free time blocks are readily accommodated by this approach.

1