Browse Prior Art Database

Supporting X.500 Resource Names Through Local Database Surrogates

IP.com Disclosure Number: IPCOM000107158D
Original Publication Date: 1992-Jan-01
Included in the Prior Art Database: 2005-Mar-21
Document File: 1 page(s) / 52K

Publishing Venue

IBM

Related People

Baker, R: AUTHOR

Abstract

The Open Systems Interconnect X.500 standard describes resource names in a distributed directory application. The resource may be of any type, such as people, printers, fax machines, and so on. In order to make the names universally unique, the standard uses a variable length identifier that represents a hierarchical structure. Whenever a name collision occurs, it is resolved by concatenating another token onto the resource name.

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

Supporting X.500 Resource Names Through Local Database Surrogates

       The Open Systems Interconnect X.500 standard describes
resource names in a distributed directory application.  The resource
may be of any type, such as people, printers, fax machines, and so
on.  In order to make the names universally unique, the standard uses
a variable length identifier that represents a hierarchical
structure. Whenever a name collision occurs, it is resolved by
concatenating another token onto the resource name.

      This approach leads to resource names that have long worst-case
names, which are not practical as database keys. In order to
accommodate large theoretical sizes, such as 32K, the database must
either sacrifice indexability or resort to overflow attributes where
the primary key is long enough to handle the average case.

      Another approach which we advocate here is to use a database
surrogate that is locally unique that maps to the X.500 name for
remote addressability and reference.  The X.500 address can either be
placed into a SQL long varying length character field, or each token
can be separated into unique fields making them available to SQL
predicate expressions.

      The local surrogate represents the Object Identifier for Office
Objects.  The mapping to the X.500 resource name also provides a
mechanism for remote references.  The attachment shows a Folder
containing two Document references, the first one being local and the
second re...