Browse Prior Art Database

Method To Support graPHIGS Distributed Application Processes In A Conference Enabled graPHIGS Application

IP.com Disclosure Number: IPCOM000112412D
Original Publication Date: 1994-May-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 4 page(s) / 163K

Publishing Venue

IBM

Related People

Fuqua, TW: AUTHOR

Abstract

graPHIGS applications may share graPHIGS resources such as Workstations, Structure Stores, Image Boards and Font Directories. Sharing resources between conference enabled applications presents a problem which must be solved by the conferencing layer.

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

Method To Support graPHIGS Distributed Application Processes In A
Conference Enabled graPHIGS Application

      graPHIGS applications may share graPHIGS resources such as
Workstations, Structure Stores, Image Boards and Font Directories.
Sharing resources between conference enabled applications presents a
problem which must be solved by the conferencing layer.

      graPHIGS resources are created on a graPHIGS nucleus by the
graPHIGS shell.  Each resource has a unique shell resource identifier
(SID) and a unique nucleus resource identifier (NID).

      graPHIGS Applications which use resources created by other
graPHIGS applications are callled DAPs (Distributed Application
Process).  A DAP must obtain the NID of a resource and then attach a
SID to the NID before the DAP is able to operate on the resource.
Once a DAP has attached the nucleus resource, then both the owning
application and the DAP may use the resource.

      A conference enabled graPHIGS application is modified such that
instead of being connected to a single graPHIGS nucleus, it is
actually connected to one or more graPHIGS nucleii.  Each application
request to create a resource is performed on each nucleus, resulting
in multiple instances of the resource, one per nucleus.  Each nucleus
names the resource according to its own convention, so the each
instance of the resource has a different NID.

        +-----------------+
           |Application Shell|
           |+-----+          |
           ||sid=1|          |
           |+-----+          | App sid=1 attached to nid=5 on nucleus
1
           +-----------------+
           |   Conf Layer    | App sid=1 attached to nid=7 on nucleus
2
           +----+-----------++    by conferencing layer
                |            \
                |             \
                |              \
                |               \
                |                \
                |                 \
                |                  \
           +----v------------+      v-----------------+
           |+-----+          |      |+-----+          |
           ||nid=5|          |      ||nid=7|          |
           |+-----+          |      |+-----+          |
           |    Nucleus 1    |      |    Nucleus 2    |
           +-----------------+      +-----------------+

      The mapping from SID to NID is performed by graPHIGS separately
for each nucleus.  Therefore the graPHIGS conference enabling layer
need not provide any support for applications whi...