Browse Prior Art Database

Distributed Hypertext Links Objects

IP.com Disclosure Number: IPCOM000107964D
Original Publication Date: 1992-Apr-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 1 page(s) / 49K

Publishing Venue

IBM

Related People

Baber, RL: AUTHOR

Abstract

When designing a hypertext link system using an object-oriented language, it is common to define an object for the link itself, as opposed to the ends of the link, which are usually visible in the form of a link marker of some type. In a distributed object-oriented environment, it becomes problematical where to store the link object for easy access, conceptual clarity, and data integrity.

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

Distributed Hypertext Links Objects

       When designing a hypertext link system using an
object-oriented language, it is common to define an object for the
link itself, as opposed to the ends of the link, which are usually
visible in the form of a link marker of some type.  In a distributed
object-oriented environment, it becomes problematical where to store
the link object for easy access, conceptual clarity, and data
integrity.

      A class hierarchy for a hypertext system in which links are
defined by objects representing the link ends was described in [*].
To extend the design for traversal of links in a distributed
environment, a temporary object is defined, called an OFFLINKS, which
is instantiated from a database table containing link traversal
information.  This information "belongs" to the node at which markers
are viewed.  The table contains link destination information for all
the markers in the applications runable at that node. When a new link
is defined, the database at the source and destination nodes is
updated.  No link object need be persistent in memory.  This avoids
the problem of ownership of such a link object; that is, whether it
resides on the source or destination node, or on a server.   Even
updating of the database tables on the two nodes at link definition
time could be discarded if it is acceptable that the same link must
be defined by users at both ends in order to be bidirectional, and
that the link behavior is not necessar...