Browse Prior Art Database

Graphical Handling of Orphans in a Distributed Computing Environment

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

Publishing Venue

IBM

Related People

Rosiles, MA: AUTHOR [+2]

Abstract

Orphans occur in a Distributed Computing Environment* (DCE) when the owner of an object is deleted. There is no way through DCE to find out which objects are orphans without attempting to access the object.

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

Graphical Handling of Orphans in a Distributed Computing Environment

      Orphans occur in a Distributed Computing Environment* (DCE)
when the owner of an object is deleted.  There is no way through DCE
to find out which objects are orphans without attempting to access
the object.

      In the base DCE function, objects become orphans when the
principal that has control permission is deleted.  When another
principal attempts to access the orphaned object, the message simply
says "invalid permission for requested action".  If the Access
Control List (ACE) of the orphan is displayed, the entry for control
permission has been changed from the deleted principal's name to a
UUID.  At this point, the user has to know this means the object is
an orphan and needs to be adopted.

      In defining a Graphical User Interface, it is desirable to make
the process of discovery of orphans and the subsequent adoption
(assignment of a new owner) as easy as possible, and occur as
naturally in the interface as possible.  There are two scenarios that
must be covered:

1.  A mass discovery of all orphaned objects, which is something an
    administrator might want to perform on a regular basis.

2.  Identification of any given object as an orphan when an action is
    attempted, since DCE prevents any further action until the object
    is adopted.

Through the Graphical User Interface, there are two ways to handle
orphans:

      One way is to provide a collection point for all orphans.  This
is a container that, when opened, will display any orphans that can
be discovered.  Once in the container, the user is given the choice
of adopting any or all orphans in the container.  This meets
requirement 1 of the problem statement.  These orphans can be
discovered eit...