Abstract: A method and apparatus for extensible inter-application link management is disclosed. The apparatus is independent of the applications that manipulates the anchors linked by the links being managed. Anchors linked may reside on the same or different computers on a network. Links managed comprise navigation links and include links. Links managed may be further extended with application defined links. Application defined links may or may not require support by additional application provided link maker programs. Application defined links may inherit linking operations managed from the navigation link, include link and other existing application defined links with or without override.

Abstract: A method and apparatus for object oriented interprocess message switching between a sender process and a plurality of receiver processes is disclosed. A sender process may address object oriented messages to a plurality of objects without knowing the identities of programs that handle or observe the object operations defined by the object types of the addressee objects, whether these programs are being executed, and how to start their execution if they are not being executed. Object operations defined by object types may be inherited from predecessor object types. Inherited object operations may also be overridden for "pre-processing" and "post-processing". One handler process and any number of observer processes are selected for each object oriented message. Handler processes are selected for object oriented notice messages as well as object oriented request messages and vice versa. Executing as well as non-executing processes (i.e. programs) are selected.

Abstract: A method and apparatus for interprocess message switching between a sender process and a plurality of receiver processes is disclosed. Messages supported comprise request and notice messages. Receiver processes supported comprise handler processes and observer processes. Request messages may be observed as well as handled, and notice messages may be handled as well as observed. Handler and observer processes may be non-executing as well as executing. Sender processes do not need to specify the identity of the receiver processes. The sender process and the receiver processes may be executed on the same computer or on two or more computers in a network.

Abstract: A method and apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes is disclosed. Messages supported may be scoped to message scopes of a message scope type of "Session" or one of a plurality of non-session message scope types including a message scope type of "File". Messages may also be scoped to message scopes of an intersection or union of message scope types. Intersection and union of message scope types comprise "File in Session" and "File or Session". Scoped messages supported further comprise request and notice messages. Receiver processes supported comprise handler processes and observer processes. Request messages may be observed as well as handled, and notice messages may be handled as well as observed. Handler and observer processes may be non-executing as well as executing. Local receiver processes are selected for session scoped messages. Remote as well as local receiver processes are selected for non-session scoped messages.