Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Distributed Assignment of Unique Invoke Identifiers for Remote Operations Service Element Messages

IP.com Disclosure Number: IPCOM000112317D
Original Publication Date: 1994-Apr-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 2 page(s) / 71K

Publishing Venue

IBM

Related People

Allen, WC: AUTHOR [+4]

Abstract

A method is disclosed that allows Invoke Identifiers for Remote Operations Service Element (ROSE) messages to be assigned uniquely by separate processes on a system. This program allows re-use of Invoke

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Distributed Assignment of Unique Invoke Identifiers for Remote Operations
Service Element Messages

      A method is disclosed that allows Invoke Identifiers for Remote
Operations Service Element (ROSE) messages to be assigned uniquely by
separate processes on a system.  This program allows re-use of Invoke

Identifiers when possible, but not before.  This program does not
require a central clearinghouse to be consulted for each Invoke
Identifier as it is needed.

      Problem: Separate applications must be able to generate Invoke
Identifiers for their operations.  Each of these Invoke Identifiers
must be unique among those presently in use on the system, not just
among those used by the specific application.  An Invoke Identifier
must not be re-used between the time it is used on the invocation of
a request and the time the invoking application has received the last
response to that request.  This can be easily accomplished by having
a single assigner of Invoke Identity would need to be consulted each
time a new identifier is needed  and informed each time an Invoke
Identifier is no longer needed.  This would require a pair of
inter-process flows for the assignment of the identifier for each
message and, potentially, another set of inter-process flows to clean
up the identifier.  This would be prohibitively expensive in a system
with a large number of applications or a large amount of traffic.

      Solution: When an application connects to the communications
infrastructure it indicates the maximum number of concurrent requests
it will need (MAX_OUTSTANDING).  The communications infrastructure
assigns a value that will be used to distinguish the space of Invoke
Identifiers used by this application from all others.  Once this has
been assigned, all of the processing occurs within the application A
...