METHOD AND APPARATUS FOR SCOPED INTERPROCESS MESSAGE SWITCHING

Abstract: A method and apparatus for scoped interprocess message switching between a sender process (42) and a plurality of receiver processes (52, 54), comprises handler processes (52) and observer processes (54). Messages (64, 65) 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. Messages (64, 65) 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 (64, 65) supported further comprise process oriented as well as object oriented request (64) and notice messages (65). Request messages (64) may be observed as well as handled, and notice messages (65) may be handled as well as observed. The sender process (42) and the receiver processes (52, 54) may be executed within the same or different sessions, on the same computer or on different computers (30, 40, 50) in a network (60).

Description: METHOD AND APPARATUS FOR SCOPED INTERPROCESS MESSAGE SWITCHING BACKGROUND QF THE INVENTION 1. FIELD OF THE INVENTION. The present invention relates to the field of computer systems. In particular, the present invention is a method and apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes. 2. ART BACKGROUND: Conventional interprocess communication facilities deliver messages in as many as three modes: broadcast to all processes, multicast to a group of processes, or point-to-point to a particular process. Except for broadcast delivery, the other two modes require the sender process to supply the identities of the receiver processes. Absent from conventional facilities is the ability for a sender process to address a scoped message to a set of receiver processes, specifying the name of the set but not the identities of the processes in the set. A process is a copy or an instance of a program, an executable file, in process of execution. A scoped message is a message having a message scope which defines the set of receiver processes eligible for receiving the scoped message. In cooperative multiprocess applications, processes executing within the same user session or in different user sessions, sometimes share common files. When one process changes one of the shared files, the other processes sharing the file being changed, whether they are executing within the same user session or in different user sessions, should be informed of the change. For example, a number of displaying processes may be displaying a shared common file for different user sessions, these displaying processes will have to update their displays, if the shared file is changed by one of the processes. To notify all these displaying processes, messages will have to be delivered within a session and across sessions. Conventional facilities require that the message be broadcast or the identities of these receiver processes be provided. The former is wasteful; the latter is difficult to implement as it requires each process to communicate its changing interest in the sharable files to all other processes, and to track the changing interests of all other processes. In cooperative multiprocess applications, the set of processes within a scope changes as processes are created or destroyed, and as processes work with one file, then another. As will be described, the present invention overcomes the disadvantages of the prior art, and provides a method and apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes. SUMMARY OF THE INVENTION It is therefore an object of the present invention to improve * interprocess message switching between a sender process and a plurality of receiver processes, in particular, to provide switching of scoped messages. It is another object of the present invention that messages may be scoped to a set of receiver processes, within a session or across sessions. These objects are realized by the method and apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes of the present invention. The preferred embodiment of the method comprises the steps of registering the receiver processes with one of a plurality of interprocess message switches, joining message scopes by the switches on behalf of the registered receiver processes, selecting the registered receiver processes by the joined switches to receive scoped messages received from the sender process, queuing copies of the received scoped messages by the selecting switches, for the selected receiver processes, executing or non-executing, signaling the selected receiver processes by the queuing switches regarding the availability of the queued scoped messages, and delivering the queued scoped messages by the signaling switches, when requested by the signaled receiver processes, to the requesting receiver processes. The scoped messages may be process oriented or object oriented. The apparatus comprises various means for accomplishing the I steps of registering, joining, selecting, queuing, signaling and delivering. For disposing the received scoped messages, the preferred embodiment of the method further comprises the steps of registering the sender process with the receiving switch, discarding scoped notice messages with no selected receiver processes by the receiving switch, and replying to scoped request messages by the receiving switch. Likewise, the apparatus further comprises various means for accompHshing the steps of registering, discarding and replying. For replying to scoped request messages with no selected handler processes, the preferred embodiment of the method further comprises the steps of updating the scoped request messages by the receiving switch with the selection/handling results, selecting the registered observer processes by the joined switches to receive the reply messages, queuing copies of the reply messages by the receiving switch for the sender process, and by the selecting switches for the selected observer processes, executing and non-executing, signaling the sender process and the executing selected observer processes by the queuing switches regarding the availability of the queued reply messages, and delivering the queued reply messages by the signaling switches, when requested by the signaled processes, to the requesting processes. Similarly, the apparatus further comprises various means for accomplishing the steps of updating, selecting, queuing, signaling and delivering. For replying to scoped request messages with selected handler processes, the preferred embodiment of the method further comprises the steps of queuing an additional copy of each of the scoped request messages by the receiving switch, pending results from the local handler processes or the handler selecting joined switches, and dequeuing the result pending scoped request messages by the receiving switch, upon receipt of the results, prior to the steps of updating, selecting, signaling, and delivering described above. Similarly, the apparatus further comprises various means for accomplishing the steps of queuing and dequeuing. Registration of the receiver processes comprises registering message patterns, signaling ways and program type identifiers. Registration of the sender process comprises registering signaling ways. Receiver and sender processes may register dynamically at their initializations or some later points during their execution. Joining message scopes by switches on behalf of the receiver processes comprises joining a plurality of message scopes of various message scope types. Message scope types comprise "Session", "File", "File in Session" and "File or Session". Message scopes comprise a particular session, a particular file, an intersection between a particular session and one or more particular files, and a union of a particular session and one or more particular files. Scoped messages comprise a plurality of message attributes describing the messages. Message attributes comprise a message identifier, a message scope type, a message sender session identifier, a message non- session scope identifier, and a message recipient. Message attributes further comprise a message class and a message state. Message classes comprise "Request" and "Notice". Message states comprise "Created", "Sent", "Handled", "Queued", "Started" and "Failed". Selection comprises selecting at most one handler process and any number of observer processes for each scoped message. Both handler processes and observer processes are selected regardless of message class. Both executing as well as non-executing processes (i.e. programs) are selected. Only local receiver processes are selected for session scoped messages. Remote as well as local receiver processes are selected for non-session scoped messages. Processes are selected by matching message attributes. Matchings are performed against the registered message patterns and the message patterns within message signatures contained in program type definitions. BRIEF DESCRIPTION OF THE DRAWINGS FIGURE 1 is a block diagram illustrating the apparatus of the present invention for scoped interprocess message switching between a sender process and a plurality of receiver processes, comprising a joining means and a plurality of interprocess message switches. FIGURE 2 is a block diagram illustrating one of the joined interprocess message switches comprising a registering means, a selecting means, a queuing means, a signaling means, a delivering means and an updating means. FIGURES 3a & 3b illustrate exemplary registrations for message patterns, signaling ways and program type identifiers, and exemplary message attributes for describing messages, used by the apparatus of the present invention. FIGURES 4a & 4b illustrate the routing of a scoped request message in the preferred embodiment of the present invention FIGURES 5a & 5b illustrate the routing of a scoped notice message in the preferred embodiment of the present invention NOTATIONS AND NOMENCLATURE The detailed description which follows is presented largely in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self- consistent sequence of steps leading to a desired result. These steps are those that require physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It proves convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, objects, characters, terms, numbers, or the like. It should be borne in mind, however, that all these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Further, the manipulations performed are often referred to in terms, such as adding or comparing, which are commonly associated with mental operations performed by a human operator. No such capability of a human operator is necessary, or desirable in most cases, in any of the operation described herein which form part of the present invention; the operations are machine operations. Useful machines for performing the operations of the present invention include general purpose digital computers or other similar devices. In all cases, it should be borne in mind that the distinction between the method operations in operating a computer and the method of computation itself. The present invention relates to method steps for operating a computer in processing electrical or other (e.g. mechanical, chemical) physical signals to generate other desired physical signals. The present invention also relates to apparatus for performing these operations. This apparatus may be specially constructed for the required purposes or it may comprise a general purpose computer as selectively activated or re-configured by a computer program stored in the computer. The algorithms presented herein are not entirely related to any particular computer or other apparatus. In particular, various general purpose machines may be used with programs written in accordance with the teaching herein, or it may prove more convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these machines will appear from the description given below. DETAILED DESCRIPTION OF THE INVENTION A method and apparatus for scoped interprocess message swit iing having particular application for switdiing scoped messages between a sender process and a plurality of receiver processes being executed in the same or different sessions, on the same or different computers in a network, is disclosed. In the following description for purposes of explanation, specific numbers, materials and configurations are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced without the specific details. In other instances, well known systems are shown in diagrammatical or block diagram form in order not to obscure the present invention unnecessarily. 1. OVERVIEW: Referring now to Figure 1, a block diagram illustrating the preferred embodiment of the apparatus for scoped interprocess message switching of the present invention 80 is shown. The apparatus 80 serves a plurality of sender processes 42, 43 sending scoped messages (not shown) to, and getting reply messages (not shown) from a plurality of receiver processes 52-55. The apparatus 80 comprises a joining means' 70, and a plurality of identical interprocess message switches 10, 11 (two shown) coupled to the joining means 70. Each switch 10 directly serves a local user session comprising the switch 10, a plurality of local sender processes 42 and a plurality of local receiver processes 52, 54. Each switch 10 indirectly serves remote user sessions through remote joined switches 11 within the remote user sessions. Similarly, a remote user session comprises the remote joined switch 11, a plurality of remote sender processes 43 and a plurality of remote receiver processes 53, 55. Processes are local to the switches within their sessions (one switch per session) and remote to the other switches within other sessions. 2. IQINING MEANS: Continuing referring to Figure 1, the joining means 70 is used by the interprocess message switches 10, 11 to join one or more non-session message scopes on behalf of locally registered receiver processes. Each of the switches 10, 11 joins a non-session message scope when one of its locally registered receiver processes 52-55 registers a message pattern with the particular non-session message scope. Each of the switches 10, 11 quits a non- session message scope when all of its locally registered receiver processes 52- 55 have unregistered message patterns with the particular non-session message scope. Message scopes and registering of receiver processes will be discussed in further details later. The joining means 70 comprises at least one joined list 74, and at least one shared messages queues 76. Each of the joined lists 76 comprises a plurality of joined records. Each joined record comprises a session identifier and a timestamp. The session identifier identifies the joining switch 10, 11, and the timestamp identifies the time the switch 10, 11 most recently joins the particular message scope. The joining switches 10, 11 join a message scope by creating a joined record in the joined list 76 for the particular message scope. Preferably, a plurality of joined lists 74 organized on a per message scope type basis is used. Additionally, each of the joined lists 74 further comprises joined sub-lists organized on a per message scope basis. Similarly, a plurality of shared program pending message queues 76 organized on a per message scope type basis is used. Each of the shared program pending message queues 76 further comprise sub-queues organized on a per message scope basis. 3. INTERPROCESS MESSAGE SWITCH: Referring now to Figure 2, a block diagram illustrating one of the identical interprocess message switches 10 is shown. The switch 10 is shown in the context of its user session comprising the switch 10, a plurality of local sender processes 42 and a plurality of local receiver processes 52, 54. The local processes 42, 52, 54 are executing on a plurality of computers 30, 40, 50 connected to a network 60. These computers 30, 40, 50 and other computers (not shown) connected to the network 60 further comprise other remote user sessions. Each of these remote user sessions comprises a remote switch (not shown), a plurality of remote sender/receiver processes (not shown). The local sender processes 42 send scoped messages 64, 65 to and get reply messages 67 from, the local receiver processes 52, 54 and the remote receiver processes. The scoped messages 64, 65 comprise scoped request messages 64, and scoped notice messages 65. Local receiver processes comprise local handler processes 52 and local observer processes 54. Similarly, remote receiver processes comprise remote handler processes and remote observer processes. The switch 10 comprises a registering means 12 comprising an interface (not shown) for receiving registrations 62 as inputs from the local processes 42, 52, 54, a selecting means 14 coupled to the updating means 18 and comprising an interface (not shown) for receiving scoped messages 64, 65 as inputs from the local sender processes 42, a queuing means 16 coupled to the selecting means 14, an updating means 18 coupled to the selecting means 14 and comprising an interface (not shown) for receiving results 66 as inputs from the local receiver processes 52, 54 and the remote switches, a signaling means 20 coupled to the registering means 12 and the queuing means 16 for outputing signals to the processes 42, 52, 54, and a delivering means 21 comprising an interface (not shown) for receiving acknowledgements from the local processes 42, 52, 54 as inputs and outputing scoped messages 64, 65 to the local receiver processes 52, 54 and reply messages 67 to the local sender processes 42. a. Registering Means: Continuing referring to Figure 2, the registering means 12 is for registering local receiver processes 52, 54 with the switch 10. Receiver processes are registered with one switch, their local switch. Registration of local receiver processes 52, 54 comprises registering at least one signaling way and at least one message pattern for each of the local receiver processes 52, 54. Additionally, registration of local receiver processes may further comprise registering a program type identifier for each of the local receiver processes 52, 54. The signaling ways describe to the switch 10, how the registering local receiver process 52, 54 is to be signaled regarding the availability of a scoped message 64, 65. The message patterns describe to the switch 10, the scoped messages 64, 65 which the registering local receiver process 52, 54 is to receive. The message pattern may describe scoped messages 64, 65 which are process oriented or object oriented. The program type identifier describes to the switch 10 the program type of the program being executed by the registering local receiver process 52, 54 by identifying the program type definition 68 of the registering local receiver process 52, 54. The program type definition 68 may be a merged object-program type definition comprising object oriented message patterns merged from object type definitions. The registering local processes 52, 54 may register dynamically during their initialization or at some later points during their execution. The registering local processes 52, 54 may add registrations 62 or delete prior registrations 62. The adding and deleting may be adding and deleting of subsets of registrations 62. For further information on the registering means, registrations comprising message patterns, signaling ways, and program type identifiers, see the Specification in co-pending U.S. Patent Application, Serial Number , filed on , 1990, entitled A Method and Apparatus for Interprocess Message Switching, and the Specification in co- pending U.S. Patent Application, Serial Number , filed on , 1990, entitled A Method and Apparatus for Object Oriented Interprocess Message Switching, which are assigned to the assignee of the present Application, Sun Microsystems, Inc., and hereby fully incorporated by reference. Referring now to Figure 3a, a local receiver process registers its interest in handling or observing messages pertaining to a particular message scope by registering message patterns 82, 84 comprising message scope type attributes 89, 91 equaling the message scope type of the particular message scope. Additionally, for non-session message scope types 91, the message patterns 84 may further comprise message non-session scope identifiers equaling the particular message scope. As described in the incorporated Specifications, upon receipt of these registrations, the registering means extracts the message patterns and stores them in tables for subsequent use by the selecting means. Preferably, message patterns with message scope types scoped to intersections or unions of session message scope type with one or more non- session message scope types may also be registered. It will be understood that intersection of session message scope type with one or more non-session message scope types is a session message scope type, whereas, union of session message scope type with one or more non-session message scope types is a non-session message scope type. Message scope types and message scopes will be discussed in further details in conjunction with message attributes. Additionally, a registered local receiver process may also widen or narrow its interest in handling or observing messages pertaining to individual non-session message scopes, by adding to 94 or deleting from % the content of the non-session message scope identifier attributes 93 in the registered message patterns. As described in the incorporated Specifications, upon receipt of these registrations, the registering means adds to or deletes from the content of the non-session message scope identifier attributes in the stored message patterns scoped to the particular non-session message scope types. Additionally, the registering means also adds to or deletes from the content of the non-session message scope identifier attributes in the stored message patterns scoped to the intersections or unions with the particular non-session message scope types. An exemplary registration ∞ntaining a plurality of message patterns scoped to different message scopes is shown in the first exemplary registration 62 in Figure 3a. The first exemplary registration 62 comprises two handle message patterns 82, 84 scoped to different message scope types, and an observe message pattern 86 not scoped to any particular message scope type. The first exemplary handle message pattern 82 contains a plurality of message attributes 83 describing to the switch that the registering local receiver process is to receive messages 64 with a message class attribute of "Request", a message operation attribute of "Create Obj", representing the action of creating an object, and a message scope type attribute of "Session". The second exemplary handle message pattern 84 contains a plurality of message attributes 85 describing to the switch that, the registering local receiver process is to receive messages 64 with a message class attribute of "Request", a message operation attribute of "Put_Contents", representing the action of writing out to an object, a message scope type attribute of "File", and a message non-session scope identifier attribute of "Alpha", representing the identifier of a particular file. The exemplary observe message pattern 86 contains a plurality of message attributes 87 describing to the switch, that the registering local process is to receive messages 65 with a message class of "Notice", a message operation attribute of "LinkChgd, NodeChgd", representing the occurrence of the events of a link change or a node change, and a message state attribute of "Handled", regardless of the message scope type (none specified). Two exemplary registrations containing addition to and deletion from message patterns scoped to a particular message scope type are also shown in the fourth and fifth exemplary registration 62 in Figure 3a. The fourth exemplary registration 62 comprises an addition 94, describing to the switch that, the file identifier of "Beta" is to be added to all message non- session scope identifier attributes in registered message patterns scoped to the message scope types "File", "File in Session" and "File or Session". "File in Session" is the intersection of the message scope type "File" and the message scope type "Session", and "File or Session" is the union of these message scope types. The fifth exemplary registration 62 comprises a deletion 96, describing to the switch that the file identifier of "Alpha" is to be deleted from all message non-session scope identifier attributes in registered message patterns scoped to the message scope types "File", "File in Session" and "File or Session". Additionally, when a local receiver process registers a program type identifier 92, the registering means also checks the shared program pending messages queues in the joining means previously described, to determine if there are messages pending for a process executing a program of the particular program type being registered. In the registration illustrated, the switch will check for messages pending for a process executing the program "Starcalc". b. Selecting Means: Referring to Figure 2 again, the selecting means 14 of a receiving switch 10 is for selecting local receiver processes 52, 54 and remote receiver processes (through the joined switches) to receive scoped messages 64, 65 received from the local sender processes 42. Selection of receiver processes comprises selecting at most one local handler process 52, and any number of local observer processes 54 for each session scoped message 64, 65. Selection of receiver processes further comprises selecting at most one local 52 or remote handler process, and any number of local 54 and remote observer processes for each non-session scoped message 64, 65. Handler processes are selected for scoped notice messages 65 as well as for scoped request messages 64. Likewise, observer processes are selected for scoped request messages 64 as well as for scoped notice messages 65. Non-executing receiver processes (i.e. programs) are selected as well as executing receiver processes. For further information on the selecting means, and the selection of local handler and observer processes, executing and non- executing, also see the incorporated Specifications in co-pending U.S. Patent Applications, Serial Number , filed on , 1990, and Serial Number , filed on , 1990. For session scoped messages 64, 65, no additional action beyond what are described in the incorporated Specification is taken by the selecting means 14 of the receiving switch 10. As a result, only local receiver processes 52, 54 are selected. For non-session scoped messages 64, 65, the selecting means 14 of the receiving switch 10 further selects joined switches and sends copies of the non-session scoped messages 64, 65 to the selected joined switches for selection of remote observer processes and remote handler processes. The selecting means 14 of the receiving switch 10 selects the joined switches for selection of remote observer processes regardless whether local receiver processes 52, 54 are selected. The selecting means 14 of the receiving switch 10 selects the joined switches for selection of remote handler processes, only if local handler processes 52 are not selected. For selection of remote observer processes, the selecting means 14 of the receiving switch 10 selects, for each of the non-session scoped messages 64, 65, all joined switches that have not been sent a copy of the non- session scoped message 64, 65. The selecting means 14 of the receiving switch 10 further comprises a checking means (not shown) coupled to the third matching means (see incorporated Specification) for determining whether a joined switch has been sent a copy of a non-session scoped message 64, 65 by comparing the content of a message dispatched list attribute of a non-session scoped message 64, 65 against the joined records in the joined lists for the particular non-session message scope. If one or more joined switches are selected for a non-session scoped message 64, 65, the checking means of the selecting means 14 of the receiving switch 10 updates a message recipient attribute in the non-session scoped messages 64, 65 to Observers Only", and the message dispatched list attribute with the session identifiers of the selected joined switches, and sends a copy of the updated non-session scoped message 64, 65 to each of the selected joined switches. The message recipient attribute and the message dispatched list attribute of a scoped message 64, 65 will be discussed in further details in conjunction with other message attributes later. For selection of remote handler processes, the selecting means 14 of the receiving switch 10 selects, for each of the non-session scoped messages 64, 65 with no local handler processes, one of the joined switches that have not been sent a copy of the non-session scoped message 64, 65. The selecting means 14 of the receiving switch 10 determines whether a joined switch has been sent a copy of a non-session scoped message 64, 65 in the same manner as described above. The checking means of the selecting means 14 of the receiving switch 10 selects one of these joined switches arbitrarily. If a joined switch is selected for a non-session scoped message 64, 65, the selecting means 14 of the receiving switch 10 updates the message recipient attribute in the non-session scoped messages 64, 65 to "Handler Only", message handler program type attributes with matching handler program types from message signature matchings and the message dispatched list attribute with the selected joined switch's session identifier, and sends a copy of the updated non-session scoped message 64, 65 to the selected joined switch. The selecting means 14 of the receiving switch 10 repeats this process until a remote handler process is selected or all the joined switches have been selected. The selecting means 14 of the receiving switch 10 being coupled to the updating means 18 receives the scoped messages 64, 65 as input again, when no remote handler processes are selected by the selected joined switches. The selecting means 14 of the receiving switch 10 may determine whether the scoped messages 64, 65 are received from the sender processes 42 or the updating means 18 in a variety of manners, including but not limited to the message state attributes. The message state attribute and the updating means 18 will be discussed in further details later in conjunction with message attributes and reply messages respectively. The non-session scoped messages 64, 65 may be sent from the receiving switch 10 to the selected joined switches using any system message sending services. Preferably, the same system message sending services used by the registering means 12, as described in the incorporated Specification, is used. Selection of remote receiver processes by the selecting means of a joined switch comprises the same steps of matching, choosing, and starting for selection of local receiver processes 52, performed by the selecting means 14 of the receiving switch 10. The selecting means of a joined switch do not select joined switches. Furthermore, if the program type definitions 68 are stored in files 24 shared among the joined switches, the selecting means of a joined switch may skip the step of message signatures matching. The selecting means of a joined switch may determine whether the scoped messages 64, 65 are received from the receiving switch 10 or its local sender processes in a variety of manners, including but not limited to the message state attribute and the message recipient attribute. The routing of session and non-session scoped request and notices messages 64, 65 to local and remote handler and observer processes will be discussed in further details later. c Queuing Means: Referring to Figure 2 again, the queuing means 16 of the receiving switch 10 is for queuing copies of the scoped messages 64, 65 with selected local receiver processes 52, 54. The queuing means 16 of the receiving switch 10 being coupled to the selecting means 14 receives the scoped messages 64, 65 and local selection results from the selecting means 14 as input. The queuing means 16 of the receiving switch 10 queues copies of the scoped messages 64, 65 with executing selected local receiver processes 52, 54 for subsequent retrieval by these local processes. The queuing means 16 of the receiving switch 10 also queues copies of the scoped messages 64, 65 with non- executing selected receiver processes (i.e. programs), if the message disposition attributes are "queue". The queuing means 16 of the receiving switch 10 queues copies of the program pending session scoped messages 64, 65 into one of a plurality of private program pending messages queues 26. The queuing means 16 of the receiving switch 10 queues copies of the program pending non-session scoped messages 64, 65 into one of the shared program pending messages queues in the joining means (see Fig 1), for the particular non-session message scopes. Similarly, the queuing means of a joined switch is for queuing copies of the scoped messages 64, 65 with selected remote receiver processes (local to the joined switch). The queuing means of a joined switch receives the scoped messages 64, 65 as input and queues copies of them in the same manner as the queuing means 16 of the receiving switch 10. For further information on the queuing means and the private program pending messages queues, also see the incorporated Specifications in co-pending U.S. Patent Applications, Serial Number , filed on , 1990, and Serial Number , filed on , 1990. d. Signaling & Delivering Means: Continuing referring to Figure 2, the signaling means 20 of the receiving switch 10 is for signaling the selected local receiver processes 52, 54 regarding the availability of a scoped message 64, 65. The signaling means 20 of the receiving switch 10 being coupled to the queuing means 16 of the receiving switch 10, receives the selected executing local receiver process identifiers from the queuing means 16 of the receiving switch 10, as input. The signaling means 20 of the receiving switch 10 being also coupled to the registering means 12 of the receiving switch 10 receives receiver processes identifiers of registering local receiver processes with program types that are matching against pending programs, from the registering means 12 of the receiving switch 10, as input. The signaling means 20 of the receiving switch 10 signals these executing local receiver processes 52, 54 regarding the availability of the queued scoped messages 64, 65. It will be understood that local receiver processes 52, 54 being started by the receiving switch 10 do not have to be signaled. The starting local receiver processes 52, 4 are "signaled" as part of the start up process. Similarly, the signaling means of a joined switch is for signaling the selected remote receiver processes (local to the joined switch). The signaling means of a joined switch receives the remote receiver processes identifiers (local to the joined switch) and signals them in the same manner as the signaling means 20 of the receiving switch 10. The delivering means 21 of the receiving switch 10 is for dequeuing the queued scoped messages 64, 65 and delivering the scoped messages 64, 65 to the selected local receiver processes 52, 54. The delivering means 21 of the receiving switch 21 comprises an interface (not shown) for receiving acknowledgements from the local receiver processes 52, 54 as inputs, indicating that the local receiver processes 52, 54 are ready to receive the queued scoped messages 64, 65. Upon receipt of the acknowledgments, the delivering means 21 of the receiving switch 10 dequeues the queued scoped messages 64, 65 and delivers the scoped messages 64, 65 to the acknowledging local receiver processes 52, 54. Similarly, the delivering means of a joined switch is for dequeuing and delivering the queued scoped messages 64, 65 to selected remote receiver processes. The delivering means of a joined switch receives acknowledgement from the signaled remote receiver processes (local to the joined switch), dequeues and delivers the scoped messages 64, 65 in the same manner as the delivering means 21 of the receiving switch 10. For further information on the signaling means, and the delivering means, also see the incorporated Specifications in co-pending U.S. Patent Applications, Serial Number , filed on , 1990, and Serial Number , filed on , 1990. 4. MESSAGE ATTJ-raπESl Referring now to Figure 3b, a block diagram illustrating exemplary message attributes used by the apparatus of the present invention for describing the scoped messages 64, 65 is shown. Each scoped message 64, 65 comprises at least one message attribute 100-130. The message attributes 100-130 comprise a message identifier 100, a message scope type attribute 102, a message recipient attribute 104, a message dispatch list attribute 106, a message sender session identifier attribute 108, a message non-session scope identifier attribute 110. Preferably, the message attributes 112-130 further comprise a message class attribute 112, a message state attribute 114, , a message operation attribute 116, a message operation argument attribute 118, message sender identifier 120, a message sender program type identifier 122, a message handler identifier 124, a message handler program type identifier 126, a message disposition attribute 128, and a message failure reason attribute 130. The message identifier 100 uniquely identifies the scoped message 64, 65. The unique message identifier 100 may be constructed in a variety of manners. Preferably, the unique message identifier 100 comprises a sender computer identifier, a sender process identifier and a sender process specific message identifier, such as a message counter, for example, Sextant.712.0001. The message scope type attribute 102 describes the message scope type of the scoped message 64, 65. Message scope types may be "Session" or one of a plurality of non-session message scope types. Non-session message scope types comprise a message scope type of Tile". The message scope type of "Session" is the defaulted message scope type, if no message scope type is specified. A "Session" message scope type describes to the switch that only local receiver processes registered with the receiving switch are to be selected. A non-session message scope type describes to the receiving switch that remote receiver processes are to be selected as well as local receiver processes. Preferably, message scope types may further comprise intersections and unions of message scope types comprising an intersection message scope type of "File in Session", and a union message scope type of "File or Session". As discussed earlier, the intersection of a non-session message scope with the "Session" message scope is a session message scope, therefore, only local receiver processes are selected for the message scope type of "File in Session"; whereas, the union of a non-session message scope with the "Session" message scope is a non-session message scope, therefore remote as well as local receiver processes are selected for the message scope type of "File or Session". The message recipient attribute 104 describes to the selecting switch, what type of receiver processes are to be selected. The message recipient attribute 104 comprises one of a plurality of recipient specifications. Recipient specifications comprise "Both Handler and Observers", "Handler Only" and "Observers Only". The recipient specification of "Both Handler and Observers" is the defaulted recipient specification, if none specified. The message dispatched list attribute 106 describes to the selecting switch, which joined switch has been sent the scoped message 64, 65 and the time at which the scoped message 64, 65 was sent. The message dispatched list attribute 104 comprises a plurality of dispatched records comprising a session identifier and a timestamp. The session identifier identifies the joined switch that has been sent the scoped message 64, 65. The timestamp marks the time the scoped message 64, 65 was sent. The message sender session identifier attribute 108 describes to the selecting switch, which session (i.e. which joined switch) the sender process is affiliated with. The session identifier may be implemented in a wide variety of manners, as long as it uniquely identifies the joined switch. The message non-session scope identifier 110 describes to the selecting switch, the particular non-session message scope that the scoped message 64, 65 is scoped to, e.g. a file identifier. Likewise, the message non- session scope identifier may be implemented in a wide variety of manners, as long as it uniquely identifies the non-session message scope. For further information on other message attributes 112-130, also see the incorporated Specifications in co-pending U.S. Patent Applications, Serial Number , filed on , 1990, and Serial Number , filed on , 1990. 5. REPLIES Referring back to Figure 2, the interprocess message switch 10 also provides specific supports for providing reply messages 67 to the scoped request messages 64. Reply messages 67 are generated by the receiving switch 10 for the local sender processes 42 for scoped request messages 64. No reply messages 67 are generated by the receiving switch 10 for the local sender processes 42 for scoped notice messages 65. Additionally, the supports for providing reply messages 67 are also used by the receiving switch 10 and the joined switches to facilitate selection of remote handler processes for scoped notice messages 65 as well as scoped request messages 64. Additional specific supports for the reply messages 67 are provided by the updating means 18 and the queuing means 16. The registering means 12, the selecting means 14, the signaling means 20, and the delivering means 21 are also used, but no additional supports beyond what has been described are required in these means. a. Updating Means: The updating means 18 of a receiving switch 10 is for generating reply messages 67 to scoped request messages 64 for the local sender processes 42. The updating means 18 of a receiving switch 10 is also for causing the selecting means 14 of a receiving switch 10 to select another joined switch. The updating means 18 of the receiving switch 10 being coupled to the selecting means 14 of the receiving switch 10 receives results of local handler processes selection from the selecting means 14 of the receiving switch 10, as input. The updating means 18 of the receiving switch 10 further comprises an interface (not shown) for receiving results 66 of remote handler processes selection from joined switches as input. The updating means 18 of the receiving switch 10 further receives through the same interface, handling results 66 from local handler processes 52 and remote handler selecting switches. Handling results 66 comprise updates of "Handled" or "Failed" to message state attributes and updates to message failure reason attributes. Message state attributes and message failure reason attributes will be discussed in further details later in conjunction with message attributes. Upon receipt of local selection results from the selecting means 14 of the receiving switch 10, indicating failure to select local handler processes 52 and joined switches (if applicable), the updating means 18 of the receiving switch 10 generates reply messages 67 to scoped request messages 64 and discards scoped notice messages 65. The updating means 18 of the receiving switch 10 generates the reply messages 67 by updating the scoped request messages 64. Updates comprise updating message state attributes to "Failed", and message failure reason attributes. Upon receipt of local selection results from the selecting means 14, indicating success in selecting local handler processes 52 or joined switches (if applicable), the updating means 18 of the receiving switch 10 takes no action. Upon receipt of the remote selection results (always equal "Failed") from a joined switch, the updating means 18 of the receiving switch 10 dequeues the results pending scoped messages 64, 65 from the results pending messages queues 26, and outputs the dequeued scoped messages 64, 65 to the selecting means 14 of the receiving switch 10. As discussed earlier, the selecting means 14 of the receiving switch 10 being coupled to the updating means 18 of the receiving switch 10 receives the dequeued scoped message 64, 65 as input for selection of the "next" joined switch. Remote selection results will be discussed in further details later in conjunction with the updating means of a joined switch. Queuing of the scoped messages 64, 65 into results pending messages queues will be discussed in further details later in conjunction with the specific supports provided for the reply messages 67 by the queuing means 16 of the receiving switch 10. Upon receipt of handling results 66 for scoped request messages 64 from local handler processes or remote handler selecting switches, the updating means 18 of the receiving switch 10 generates the reply messages 67. The updating means 18 of the receiving switch 10 dequeues the results pending scoped request messages from results pending messages queues 26 and generates the reply messages 67 by updating the scoped request messages 64 according to the handling results 66 received. The updating means of a joined switch is used for providing remote selection and handling results 66 for scoped request and notice messages 64, 65 to the receiving switch 10. The updating means of a joined switch being coupled to the selecting means of the joined switch receives results of remote handler processes selection (local to the joined switch) from the selecting means of the joined switch, as input. The updating means of a joined switch further comprise an interface (not shown) for receiving remote handling results from remote handler processes (local to the joined switch). Upon receipt of selection results from the selecting means of a joined switch, indicating failure to select local handler processes (remote to the receiving switch 10), the updating means of the joined switch sends the selection results 66 for the scoped messages 64, 65 to the receiving switch 10. Upon receipt of selection results from the selecting means of a joined switch, indicating success in selecting local handler processes (remote to the receiving switch 10), the updating means of the joined switch generates handling results to the scoped notice messages 65 and sends the handling results 66 to the receiving switch 10; no action is taken for scoped request messages 64. Upon receipt of local handling results from local handler processes of a joined switch (remote to the receiving switch 10), the updating means of the joined switch dequeues the results pending scoped request messages 64 from results pending messages queues, generates the remote handling results 66 based on the local handling results received and sends the remote handling results 66 to the receiving switch 10. Similar to the selecting means, the updating means may determine whether the switch is a receiving switch 10 or a joined switch in a variety of manners, including but not limited to the message state and recipient attributes. b. Other Means: Continuing referring to Figure 2, to support replying to the scoped request messages 64, the registering means 12 is also for registering the local sender process 42 with the receiving switch 10. Similar to the local receiver processes 52, 54, a local sender process is registered with one switch. Registration of local sender processes 42 comprises registering at least one signaling way for each of the local sender processes 42. Additionally, the queuing means 16 of the receiving switch 10 queues additional copies of the scoped messages 64, 65 sent to the joined switches for selection of remote handler processes, pending receipt of results 66 from the joined switches. The queuing means 16 of a handler selecting receiving switch 10 also queues additional copies of the scoped request messages 64 with selected local handler processes 52, pending receipt of results 66 from the local handler processes 52. Similarly, the queuing means of a handler selecting joined switch queues additional copies of the scoped request messages 64 with selected local handler processes (remote to the receiving switch 10) in the same manner as the receiving switch 10. The selecting means 14 of the receiving switch 10 is also for selecting any number of local observer processes 54 and joined switches (if applicable) to receive copies of the reply messages 67 generated by the receiving switch 10 for the local sender processes 42. Similarly, the selecting means of a joined switch is for selecting remote observer processes (local to the joined switch) to receive copies of the reply messages 67. Selection of local and remote observer processes for reply messages 67 comprises the same steps for selecting local and remote observer processes for the original scoped messages 64, 65. As discussed earlier, reply messages 67 are generated by updating the scoped request messages 64, therefore, reply messages 67 are scoped to the same message scope types and message scopes, as the original scoped request messages 64. Thus, reply messages 67 to non-session scoped request messages 64 are also forwarded to other joined switches for selection of remote receiver processes. The queuing means 16 of the receiving switch 10 is also for queuing copies of the reply messages 67 for the original local sender processes 42 and selected local observer processes 54. Similarly, the queuing means of a joined switch is also for queuing copies of the reply messages 67 for selected remote observer processes (local to the joined switch). The signaling means 20 of the receiving switch 10 is also for signaling the original local sender processes 42, and the selected executing local observer processes 54 regarding the availability of the queued reply messages 67. Likewise, the signaling means of a joined switch is for signaling the selected executing remote observer processes (local to the joined switch). The delivering means 21 of the receiving switch 10 is also for dequeuing and delivering the queued reply messages 67 upon request of the signaled local processes 42, 54, to the requesting local processes 42, 54. Similarly, the delivering means of a joined switch is also for dequeuing and delivering the queued reply messages 67 upon request of the signaled remote processes (local to the joined switch), to the requesting remote processes (local to the joined switch). For further information on replying to request messages, also see the incorporated Specifications in co-pending U.S. Patent Applications, Serial Number , filed on , 1990, and Serial Number , filed on , 1990. 6. SCOPED REQUEST MESSAGE ROUTING; Referring now to Figures 4a & 4b, two block diagrams summarizing the routing and disposition of a scoped request message are shown. The scoped request messages 64-1 to 64-6, the results 66-1 to 66-3, and the reply messages 67-1 to 67-5, relate to the scoped request messages 64, the results 66 and the reply messages 67 of Figure 2. Likewise, the handler processes 52-1, 52-2, 53-1, 53-2 and the observer processes 54-1, 54-2, 55-1, 55-2 relate to the handler processes 52, 53 and the observer processes 54, 55 of Figure 1. a. Receiving Switch: Referring first to Figure 4a, initially, the scoped request message with a message state attribute of "Created" 64-1 is sent to the receiving switch 10 as input. Copies of the scoped request message with the message state attribute changed to "Sent" 64-4 are eventually routed to all selected local observer processes 54-1. If the scoped request message is scoped to a non- session message scope, copies of the scoped request message 64-3 with the message state attribute changed to "Sent", and message recipient attribute changed to "Observers Only" are also sent to the all joined switches that have not been sent the non-session scoped request message, for continued selection and routing to remote observer processes. If local handler processes 52-1, 52-2 are found, one copy of the scoped request message with the message state attribute changed to "Sent" 64- 2 is eventually routed to the local handler process with the highest ranking 52-1. No copy of the scoped request message 64-2 is routed to the other eligible local handler processes with lower rankings 52-2. If no local handler process is selected by the receiving switch 10 and the scoped request message is scoped to a message scope of "Session", the receiving switch updates the message state attribute to "Failed" and generates a reply message 67-1. The reply message with a message state attribute of "Failed" 67-1 is eventually routed back to the originating local sender process 42. If no local handler process is selected by the receiving switch 10, the scoped request message is scoped to a non-session message scope, and there are other joined switches, the scoped request message 64-3 with the message state attribute changed to "Sent", and the message recipient attribute updated to "Handler Only", is sent to one of the joined switches that has not been sent the non-session scoped request message 64-3, for continued selection and routing to a remote handler process. As described earlier, the joined switch being sent the non-session scoped request message 64-3 is selected arbitrarily from all the joined switches that have not received the non-session scoped request message 64-3. The process is repeated until a remote handler process is found or all these joined switches have been selected. The receiving switch 10 is provided with the remote selection results 66-1 when remote handler processes are not found, by the selected joined switches . Similarly, if no remote handler process is selected by any of the joined switches for the non-session scoped request message 64-3, the receiving switch 10 updates the message state attribute to "Failed" and generates a reply message 67-1. The reply message with a message state attribute of "Failed" 67- 1 is eventually routed back to the originating local sender process 42. If the scoped request message is handled locally, the handling result 66-1 is sent from the local handler process 52-1 to the receiving switch 10 as input. If the scoped request message is handled remotely, the handling result 66-1 is sent from the handler selecting joined switch to the receiving switch 10 as input. In either case, the receiving switch 10 updates the message state attribute to "Handled" or "Failed" and generates a reply message 67-2. Copies of the reply message with a message state attribute "Handled" or "Failed" 67-2, 67-3, are eventually routed to all selected local observer processes 54-2, as well as the originating sender process 42. If the reply message 67-2 is a reply message to a non-session scoped request message and there are joined switches that have not received a copy of the reply message 67-2, a copy of the reply message 67-2 with the message recipient attribute changed to "Observers Only" is also sent to all the joined switches that have not received a copy of the reply message 67-2, for continued selection of remote observer processes. b. Joined Switch: Referring now to Figure 4b, upon receipt of a non-session scoped request message 64-4 with a message recipient attribute of "Observers Only" from the receiving switch, copies of the non-session scoped request message 64-6 are eventually routed to selected local observer processes (remote to the receiving switch) 55-1. If a non-session scoped request message 64-4 with a message recipient attribute of "Handler Only" is received from the receiving switch, one copy of the scoped request message with the message state attribute changed to "Sent" 64-5 is eventually routed to the local handler process (remote to the receiving switch) with the highest ranking 53-1, if local handler processes 53-1, 52-2 (remote to the receiving switch) are found. Similarly, no copy of the scoped request message 64-5 is routed to the other eligible local handler processes (remote to the receiving switch) with lower rankings 53-2. Additionally, results of the selection 66-3 are sent by the joined switch 11 to the receiving switch, when the joined switch 11 fails to select a local handler process (remote to the receiving switch). If the scoped request message is handled locally (remote to the receiving switch), the result 66-2 is sent from the local handler process 53-1 (remote to the receiving switch) to the joined switch 11 as input. The joined switch 11 forwards the received results 66-3 to the receiving switch. Similarly, upon receipt of a non-session scoped reply message 67- 5 with a message recipient attribute of "Observers Only" from the receiving switch, copies of the non-session scoped reply message 67-4 are eventually routed to selected local observer processes (remote to the receiving switch) 55- 2. 7. SCOPED NOTICE MESSAGE ROUTING: Referring now to Figures 5a & 5b, two block diagrams summarizing the routing and disposition of a scoped notice message is shown. Like Figures 4a & 4b, the scoped notice messages 65-1 to 65-7, and the results 66-1 to 66-2, relate to the scoped notice messages 65, and the results 66 in Figure 2. Similarly, the handler processes 52-1, 52-2, 53-1, 53-2 and the observer processes 54-1, 55-1 relate to the handler processes 52, 53 and the observer processes 54, 55 in Figure 1. a. Receiving Switch: Referring first to Figure 5a, initially, similar to a scoped request message, a scoped notice message with a message state attribute of "Created" 65-1 is sent to the receiving switch 10 as input. Similarly, copies of the scoped notice message with the message state attribute changed to "Sent" 65-3 are eventually routed to all selected local observer processes 54-1. If the scoped notice message is scoped to a non-session message scope, and there are joined switches, a copy of the scoped notice message 65-4 with the message state attribute changed to "Sent" and the message recipient attribute changed to "Observers Only", is sent to all the joined switches that have not been sent the non-session scoped notice message, for continued selection of remote observer processes. Likewise, only one copy of the scoped notice message with the message state attribute changed to "Sent" 65-2 is also eventually routed to one selected local handler process 52-1. No copy of the scoped notice message 65-2 is routed to the other eligible local handler processes with lower rankings 52- 2. Unlike a scoped request message, if the scoped notice message is scoped to a message scope of "Session" and handler process 52-1, 52-2 are not selected, the scoped notice message 65-5 is discarded. If the scoped notice message is scoped to a non-session message scope and handler processes 52-1, 52-2 are not selected, the scoped notice message 65-5 is also discarded if there is no joined switch. Similar to a scoped request message, if the scoped notice message is scoped to a non-session message scope, no local handler process 52-1, 52-2 is selected and there is at least one joined switch, a copy of the non-session scoped notice message 65-4 with the message state attribute updated to "Sent", and the message recipient attribute changed to "Handler Only", is sent to one of the joined switches for continued selection of remote handler processes. As described earlier, the joined switch being sent the non-session scoped notice message 65-4 is selected arbitrarily from all the joined switches that have not received the non-session scoped notice message 65-4. The process is repeated until a remote handler process is found or all these joined switches have been selected. The receiving switch 10 is provided with the selection results 66-1 when remote handler process is not found, by the selected joined switches. Also unlike a scoped request message, the selected local handler process 52-1 and the selected joined switch, does not provide handling results to a scoped notice message after the scoped notice message is handled. b. Joined Switch: Referring now to Figure 5b, upon receipt of a non-session scoped notice message 65-6 with a message recipient attribute of "Observers Only" from the receiving switch, copies of the non-session scoped notice message 65-8 are eventually routed to any selected local observers 55-1 (remote to the receiving switch). If a non-session scoped notice message 65-6 with a message recipient attribute of "Handler Only" is received, one copy of the scoped notice message with the message state attribute changed to "Sent" 65-7 is also eventually routed to one selected local handler process 53-1 (remote to the receiving switch). Again, no copy of the scoped notice message 65-7 is routed to the other eligible local handler processes (remote to the receiving switch) with lower rankings 53-2. Additionally, results of the selection 66-2 is sent by the joined switch 11 to the receiving switch when a handler process is not found. Further, handling results 66-2 are generated and sent by the joined switch 11 to the receiving switch when a handler process is found. After handling the non-session scoped notice message, the selected local handler process 53-1 (remote to the receiving switch) does not provide handling results to the joined switch 11. 8. OBTECT ORIENTED MESSAGES: The method and apparatus described above can also be applied to object oriented messages. The preferred embodiment of the method will then comprise the steps of merging object type definitions and program type definitions, registering a program type identifier for each of the receiver processes with an apparatus for object oriented interprocess message switching, selecting the receiver processes to receive object oriented messages received from the sender process, queuing copies of the received object oriented messages for the selected receiver processes, executing or non- executing, signaling the selected receiver processes regarding the availability of the queued object oriented messages, and delivering the queued object oriented messages when requested by the signaled receiver processes, to the requesting receiver processes. The apparatus comprises various means for accomplishing the steps of merging, registering, selecting, queuing, signaling, and delivering. For disposing the received object oriented messages, the preferred embodiment of the method further comprises the steps of registering the sender process, discarding object oriented notice messages and replying to object oriented request messages. Likewise, the apparatus further comprises various means for accomplishing the steps of registering, discarding and replying. For replying to object oriented request messages with no selected handler processes, the preferred embodiment of the method further comprises the steps of generating reply messages by updating the object oriented request messages with selection results, queuing copies of the reply messages for the sender process, signaling the sender process regarding the availability of the queued reply messages, and delivering the queued reply messages when requested by the signaled process. Similarly, the apparatus further comprises various means for accomplishing the steps of updating, selecting, signaling and delivering. For replying to object oriented request messages with selected handler processes, the preferred embodiment of the method further comprises the steps of queuing an additional copy of each of the object oriented request messages pending results, and dequeuing the result pending object oriented request messages upon receipt of the handling results from the handler processes, prior to the steps of updating, selecting, signaling, and delivering described above. Additionally, the reply messages are generated by updating the object oriented request messages with handling results. Similarly, the apparatus further comprises various means for accomplishing the steps of queuing and dequeuing. Object type definitions comprise object type identifiers and object operation handle and observe signatures. Object operation signatures may be explicit or inheriting. Program type definitions comprise program type identifiers, and start up parameters. Merged object type-program type definitions comprise program type identifiers, start up parameters, merged object oriented message handle and observe signatures. Registration of the receiver processes comprises registering program type identifiers, signaling ways and object oriented message patterns. Registration of the sender process comprises registering signaling ways. Receiver and sender processes may register dynamically at their initialization or some later points during their execution. Object oriented messages comprise a plurality of message attributes describing the messages. Message attributes comprise a message identifier, a message object identifier attribute, a message object type attribute, and a message predecessor attribute. Message attributes further comprise a message class, a message state, a message operation attribute, and a message operation argument attribute. Message classes comprise "Request" and "Notice". Message states comprise "Created", "Sent", "Handled", "Queued", "Started" and "Failed". Selection comprises selecting at most one handler process and any number of observer processes for each object oriented message. Both handler processes and observer processes are selected regardless of message class. Both executing as well as non-executing processes are selected. Predecessor processes and inheriting processes are selected accordingly depending on the nature of inheritance. Processes are selected by matching message attributes. Matchings are performed against registered object oriented message signatures contained in merged object type-program type definitions and object oriented message patterns. 9. VARIATIONS? While the apparatus for scoped interprocess message switching of the present invention has been described in terms of a preferred embodiment, it will be understood that the present invention is not limited to the session and non-session message scope types discussed herein. The present invention is also not limited to processes executing in different sessions, on different computers, communicating across a network. Those skilled in the art will recognize that the invention can be practiced with modification and alteration within the spirit and scope of the appended claims to serve a wide variety of scoped interprocess communication situations for processes being executed by the same computer and for processes being executed by different computers in a network.

Claims: WHAT IS CLAIMED IS 1. A method for scoped interprocess message switching between a sender process and a plurality of receiver processes, said method comprising the steps of: registering each of said receiver processes with at most one of a plurality of interprocess message switches; joining message scopes by said switches on behalf of said registered receiver processes; selecting said registered receiver processes by said joined switches, to receive scoped messages received from said sender process; queuing copies of said received scoped messages with selected receiver processes; signaling said selected receiver processes by said queuing switches, regarding the availability of said queued scoped messages; and delivering said queued scoped messages by said signaling switches, upon request of said signaled receiver processes, to said requesting receiver processes. 2. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 1, wherein said step of registering said receiver processes with at most one of a plurality of interprocess message switches comprises registering with one of said switches, by each of said receiver processes dynamically at their initialization and during their execution. 3. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 1, wherein said step of registering said receiver processes with at most one of a plurality of interprocess message switches further comprises registering at least one signaling way with one of said switches, for each of said receiver processes, said signaling ways describing how said registering receiver processes are to be signaled regarding the availability of said queued scoped messages for said registering receiver processes. 4. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 3, wherein said step of registering said receiver processes with at most one of a plurality of interprocess message switches further comprises registering at least one message pattern with the same switch where said signaling ways are registered, for each of said receiver processes, said message patterns comprising a plurality of message attributes describing said scoped messages which said registering receiver processes are to receive, said message attributes comprising a message scope type attribute, a message sender session identifier, and a message non-session scope identifier. 5. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 3, wherein said step of registering said receiver processes with at most one of a plurality of interprocess message switches further comprises registering a program type identifier with the same switch where said signaling ways are registered, for each of said receiver processes, said program type identifiers identifying the programs being executed by said registering receiver processes, said registering switches generating and registering message patterns for said registering receiver processes, using message signatures contained within program type definitions comprising matching program type identifiers, said program type definitions being stored in files accessible to said registering switches. 6. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 5, wherein each of said stored program type definitions further comprises a set of program start up parameters and at least one message signature, each of said message signatures comprising one of said message patterns and a message disposition attribute. 7. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 1, wherein said step of registering said receiver processes with at most one of a plurality of interprocess message switches comprises adding registrations for said receiver processes. 8. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 7, wherein said step of registering said receiver processes with at most one of a plurality of interprocess message switches further comprise deleting said registrations. 9. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 8, wherein said adding and deleting of registrations comprise adding and deleting of subsets of said registrations, said subsets comprising message non-session scope identifiers, said message non-session scope identifiers comprising file identifiers. 10. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 1, wherein said step of joining message scopes by said switches on behalf of said registered receiver processes comprises adding joined records to at least one shared joined list for said joining switches, said joined records being added when message patterns having message scope type attributes not equaling "Session" are registered with said switches. 11. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 10, wherein each of said joined records comprises an identifier for each of said joined switches, and a timestamp marking joining time, each of said joined switch identifiers comprising a session identifier. 12. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 10, wherein said shared joined lists comprise a plurality of shared lists, shared among said joined switches, and organized on a per message scope type basis. 13. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 12, wherein said message scope types comprise a non-session message scope type of "File". 14. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 13, wherein said shared joined list for said non-session message scope type equaling "File" comprises a plurality of shared joined sub-lists, shared among said switches joined to message scopes of said non-session message scope type equaling "File", and organized on a per file basis. 15. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 1, wherein each of said scoped messages received from said sender process comprises, an identifier for said received scoped message comprising a sender computer identifier, a sender process identifier and a sender process specific message identifier; a message scope type attribute comprising one of a plurality of message scope types, said message scope types comprising a scope type of "Session", a scope of "File", a scope type of "File in Session" and a scope type of "File or Session"; a message sender session identifier attribute comprise a session identifier; a message recipient attribute comprising one of a plurality of recipient specifications, said recipient specifications comprising a recipient specification of "Handler Only", a recipient specification of "Observers Only", and a recipient specification of "Both Handler and Observers"; and a message dispatched list attribute comprising a plurality of dispatched records, each of said dispatched records comprising a session identifier for one of said switches, and a timestamp. 16. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 15, wherein said message attributes in some of said received scoped messages further comprise a message non-session scope identifier attribute comprising one of a plurality of non-session scope identifiers, said non-session scope identifiers comprising file identifiers. 17. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 15, wherein said message attributes in some of said received scoped messages further comprise a message class attribute, each of said message classes being one of a plurality of message classes comprising a message class of "Request" and a message class of "Notice". 18. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 15, wherein said message attributes in some of said received scoped messages further comprise a message state attribute, each of said message states being one of a plurality of message states comprising a state of "Created", a state of "Sent", a state of "Handled", a state of "Failed", a state of "Started", and a state of "Queued". 19. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 15, wherein said message attributes in some of said received scoped messages further comprise a message operation attribute and a message argument attribute. 20. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 15, wherein said message attributes in some of said received scoped messages further comprise an identifier for said sender process. 21. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 15, wherein said message attributes in some of said received scoped messages further comprise a program type identifier for said sender process. 22. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 15, wherein said message attributes in some of said received scoped messages further comprise an identifier for a handler process. 23. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 15, wherein said message attributes in some of said received scoped messages further comprise a program type identifier for said handler process. 24. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 15, wherein said message attributes in some of said received scoped messages further comprise a message disposition attribute, each of said message dispositions being one of a plurality of message dispositions comprising a disposition of "Queue", a disposition of "Start", and a disposition of "Discard", said disposition of "Discard" being the defaulted disposition if no disposition is specified. 25. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 15, wherein said message attributes in some of said received scoped messages further comprise a message failure reason attribute. 26. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 1, wherein said step of selecting said registered receiver processes by said joined switches comprises selecting at most one handler process by at most one of said joined switches. 27. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 26, wherein said handler process is selected for each of said received scoped messages having a message class attribute equaling "Notice" as well as equaling "Request". 28. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 26, wherein said step of selecting said registered receiver processes by said joined switches further comprises selecting any number of observer processes by said joined switches. 29. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 28, wherein said observer processes are selected for each of said received scoped messages having a message class attribute equaling "Request" as well as equaling "Notice". 30. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 28, wherein said selecting of at most one handler process and any number of observer processes comprises selecting non-executing as well as executing handler and observer processes. 31. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 1, wherein said step of selecting said registered receiver processes by said joined switches comprises the step of matching message attributes in said received scoped messages by said receiving switches, against message attributes in message patterns registered by said receiver processes with said receiving switches. 32. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 31, wherein said step of selecting said registered receiver processes by said joined switches further comprises the steps of, matching said message attributes in said received scoped messages by said receiving switches, against said message attributes in said message patterns contained in message signatures, said message signatures being contained in stored program type definitions accessible to said receiving switches; and matching program type identifiers contained in said stored program type definitions having said matching message attributes, by said receiving switches, against program type identifiers of programs being executed by said registered receiver processes. 33. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 32, wherein said step of selecting said registered receiver processes by said joined switches further comprises the step of choosing one handler process by said receiving switches, said one handler process being chosen by ranking said matching message attributes of said matching message patterns and said matching message signatures, said one handler process further being chosen arbitrarily, if said rankings of said matching message attributes are tied. 34. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 33, wherein said step of selecting said registered receiver processes by said joined switches further comprises the step of starting said receiver processes by said receiving switches, for said received scoped messages, said receiver processes being started comprise said receiver processes executing said programs identified by said stored program type definitions with said matching message signatures, said programs not being executed by other registered receiver processes, said matching message signatures comprising message disposition attributes of "Start". 35. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 34, wherein said step of selecting said registered receiver processes by said joined switches further comprises the steps of selecting said joined switches that have not been sent said received scoped messages by said receiving switches, updating message recipient attributes to "Observers Only" and message dispatched list attributes with sessions identifiers of said selected joined switches by said receiving switches, and sending said updated scoped messages to said selected joined switches by said receiving switches for continued selection of remote observer processes; said received scoped messages being scoped to non-session message scopes. 36. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 35, wherein said step of selecting said registered receiver processes by said joined switches further comprises the steps of arbitrarily selecting one of said joined switches that have not been sent said scoped messages by said receiving switches for each of said received scoped messages, updating message recipient attributes to "Handler Only" and message dispatched list attributes with sessions identifiers of said selected joined switches by said receiving switches, and sending each of said updated scoped messages to said selected joined switches by said receiving switches for continued selection of remote handler processes; said received scoped messages being scoped to non-session message scopes and no local handler processes being selected. 37. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 36, wherein said step of selecting said registered receiver processes by said joined switches further comprises the steps of repeating said steps of selecting, updating and sending, for remote handler processes selection, by said receiving switches, until a handler process is found or all of said joined switches have been selected. 38. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 37, wherein said step of selecting said registered receiver processes by said joined switches further comprises the steps of repeating said message pattern matching and choosing by said joined switches for said updated scoped messages sent, and providing said receiving switches with results of selection of handler processes for said updated scoped messages sent by said joined switches, when said joined switches fail to select handler processes. 39. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 1, wherein said step of queuing copies of said received scoped messages with selected receiver processes by said selecting switches comprises queuing copies of said received scoped messages with selected receiver processes into at least one undelivered messages queue, by said selecting switches, for subsequent retrieval by said selected receiver processes. 40. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 39, wherein said undelivered messages queues comprise a plurality of private lists, for each of said selecting switches, organized on a per process basis. 41. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 39, wherein said step of queuing copies of said received scoped messages with selected receiver processes by said selecting switches further comprises queuing copies of said received scoped messages with selected receiver processes into at least one program pending messages queue by said selecting switches, for subsequent retrieval by said selected receiver processes, said received scoped messages with selected receiver processes having their copies queued into said program pending messages queues comprise said received scoped messages comprising message attributes matching against message signatures, said matching message signatures further comprising message disposition attributes equaling "Queue"s, and being contained in program type definitions identifying programs not being executed by said registered receiver processes. 42. The method for scoped interprocess message switcihing between a sender process and a plurality of receiver processes as set forth in Claim 41, wherein said program pending messages queues comprise a plurality of private lists, for each of said selecting switches, organized on a per program type identifier basis, where said program pending messages comprising message scope type attributes equaling "Session"s are queued. 43. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 42, wherem said program pending messages queues further comprise a plurality of shared lists, shared among said selecting switches, organized on a per message scope type basis, where said program pending messages comprising said message scope type attributes not equaling "Session"s are queued. 44. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 43, wherein said non-session shared lists comprise a list for one of said message scope types equaling "File". 45. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 44, wherein said "File" scoped list comprises a plurality of shared sub-lists, shared among said selecting switches, organized on a per file basis. 46. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 39, wherein said step of queuing copies of said received scoped messages with selected receiver processes by said selecting switches comprises queuing copies of said received scoped messages with selected joined switches into at least one results pending messages queue, by said receiving switches,; said selected joined switches being selected for remote handler processes selection, said pending results comprising selection and handling results. 47. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 46, wherein said results pending messages queues comprise a plurality of private lists, for each of said receiving switches, organized on a per process basis. 48. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 1, wherein said step of signaling said selected receiver processes by said queuing switches comprises posting of events by said queuing switches, for detection by said selected receiver processes using system event detection services. 49. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 1, wherein said step of delivering said queued scoped messages by said signaling switches comprises dequeuing said queued scoped messages and sending said dequeued scoped messages by said signaling switches, to said selected receiver processes, using system message sending services. 50. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 1, wherein said method further comprises the step of discarding said received scoped messages by said receiving switches, said received scoped messages being discarded comprising said received scoped messages having message class attributes equaling "Notice"s and no selected receiver processes, said receiving switches receiving results of remote handler processes selection from said joined switches, when said joined switches fail to select handler processes. 51. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 50, wherein said received scoped "Notice" messages with no selected receiver processes comprise said received scoped "Notice" messages having message attributes non-matching against registered message patterns with said selecting switches and non-matching against message signatures contained in program type definitions, said program type definitions being stored in files accessible to said selecting switches. 52. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 51, wherein said received scoped "Notice" messages with no selected receiver processes further comprise said received scoped "Notice" messages having said message attributes matching against said message signatures, said matching message signatures further comprising said message dispositions equaling "Discard"s, and being contained in said program type definitions identifying said programs not being executed by said registered receiver processes. 53. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 1, wherein said method further comprises the steps of replying to said received scoped messages with message class attributes equaling "Notice"s by said joined switches, when said joined switches select handler processes for said scoped messages. 54. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 53, wherein said replying to said received scoped messages with message class attributes equaling "Notice"s by said joined switches comprises the steps of generating reply messages by updating said scoped "Notice" messages, said updating comprising updating message state attributes to "Handled"s; and sending said generated reply messages to said receiving switches. 55. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 1, wherein said method further comprises the steps of, registering said sender process with said receiving switches; and replying to said received scoped messages with message class attributes equaling "Requesf's by said receiving switches. 56. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 55, wherem said step of registering said sender process with said receiving switches comprises registering with said receiving switches, by said sender process dynamically at its initialization and during its execution. 57. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 55, wherein said step of registering said sender process comprises registering at least one signaling way for said sender process, said signaling ways describing how said registering sender process is to be signaled regarding the availability of queued reply messages. 58. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 55, wherein said step of replying to said received scoped "Request" messages by said receiving switches comprises replying to said "Request" messages with no selected handler process by said receiving switches. said receiving switches receiving results of remote handler processes selection from said joined switches, when said joined switches fail to select handler processes. 59. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 58, wherein said received scoped "Request" messages with no selected handler process comprise said received scoped "Request" messages having message attributes non-matching against registered message patterns with said selecting switches and non-matching against said message signatures contained in program type definitions, said program type definitions being stored in files accessible to said selecting switches. 60. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 59, wherein said received scoped "Request" messages with no selected handler process further comprise said received scoped "Request" messages having said message attributes matching against said message signatures, said matching message signatures further comprising said message dispositions equaling "Discard"s, and being contained in said program type definitions identifying said programs not being executed by said registered receiver processes. 61. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 58, wherein said step of replying to said received scoped "Request" messages by said receiving switches further comprises replying to said received scoped "Request" messages with selected handler processes, said receiving switches receiving results of handling from local handler processes and remote handler selecting switches, said remote handler selecting switches receiving results of handling from remote handler processes. 62. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 55, wherein said step of replying to said received scoped "Request" messages by said receiving switches comprises the steps of, generating reply messages to said received scoped "Request" messages by said receiving switches; selecting said registered received processes to receive said reply messages by said joined switches; queuing said reply messages to at least one undelivered messages queue, for subsequent retrieval by said sender process and said selected receiver processes by said selecting switches for said reply messages; signaling said sender process and said selected receiver processes regarding the availability of said queued reply messages by said queuing switches for said reply messages; and delivering said queued reply messages by said signaling switches for said queued reply messages, upon request of said signaled processes, to said requesting receiver processes. 63. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 62, wherein said step of generating reply messages by said receiving switches comprises the steps of, dequeuing said received scoped message from results pending messages queues, and updating message attributes of said received scoped "Request" messages with no selected handler process by said receiving switches; said message attributes being updated according to results of local handler processes selection and remote handler processes selection, said message attributes being updated comprising message state attributes being updated to "Failed"; said receiving switches receiving said results of remote handler processes selection from said joined switches, when said joined switches fail to select handler processes. 64. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 62, wherein said step of generating reply messages by said receiving switches further comprises steps of dequeuing said received scoped message from results pending messages queues, and updating message attributes of said received scoped "Request" messages with selected handler process by said receiving switches; said message attributes being updated according to handling results received from local handler processes and remote handler selecting switches, said message attributes being updated comprising message state attributes being updated to one of a plurality of message states comprising a state of "Handled" and a state of "Failed"; said receiving switches receiving said handling results from said local handler processes and said joined switches, said joined switches receiving said handling results from said remote handler processes. 65. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 64, wherein said step of generating reply messages by said receiving switches further comprises the step of queuing another copy of each of said received scoped "Request" messages with selected local handler processes, by said receiving switches, pending receipt of said handling results from said local handler processes. 66. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 65, wherein said step of queuing copies of said received scoped "Request" messages with local handler processes by said receiving switches comprises queuing said copies in the same results pending messages queues for queuing said received scoped messages with selected joined switches for remote handler processes selection. 67. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 64, wherein said step of generating reply messages by said receiving switches further comprises the step of queuing another copy of each of said received scoped "Request" messages with selected handler processes, by said remote handler selecting switches, pending receipt of said handling results from remote handler processes. 68. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 67, wherein said step of queuing copies of said received scoped "Request" messages by said remote handler selecting switches comprises queuing said copies in at least one results pending messages queue by said remote handler selecting switches. 69. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 68, wherein said results pending messages queues comprise a plurality of private lists, for each of said remote handler selecting switches, organized on a re¬ process basis. 70. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 62, wherein said step of selecting said registered receiver processes by said joined switches, to receive said reply messages, comprises selecting any number of observer processes by said joined switches, to receive said reply messages. 71. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 70, wherein said selecting any number of observer processes by said joined switches, to receive said reply messages, comprises the same steps for selecting said registered receiver processes by said joined switches, to receive said received scoped messages. 72. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 62, wherein said step of queuing copies of said updated messages, by said selecting switches having selected receiver processes for said reply messages, comprises queuing copies of said reply messages into the same undelivered messages queues, for queuing copies of the said received scoped messages with selected receiver processes, by said selecting switches having selected receiver processes for said received scoped messages. 73. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 62, wherein said step of signaling said sender process and selected receiver processes, by said queuing switches having queued copies of said reply messages, comprises the same posting of events by said queuing switches having queued copies of said received scoped messages, for signaling said selected receiver processes regarding the availability of said queued scoped messages. 74. The method for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 62, wherein said step of delivering said queued reply messages by said signaling switches for said reply messages comprises the same steps of delivering said queued scoped messages received from said sender process. 75. An apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes, said apparatus comprising: a plurality of substantially identical interprocess message switches for receiving scoped messages from said sender process and delivering to said receiver processes; and means coupled to said switches for joining said switches to non-session message scopes, said joining means comprising at least one shared joined list. 76. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 75, wherein each of said shared joined lists comprise a plurality of joined records, said joined records being added when message patterns having said non- session message scopes are registered with said switches, and said switches not joined to said non-session message scopes. 77. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 76, wherein each of said joined records comprises an identifier of one of said joined switches and a timestamp marking joining time, each of said joined switch identifiers comprising a session identifier. 78. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 77, wherein said shared joined lists comprise a plurality of shared lists, shared among said joined switches, and organized on a per message scope type basis. 79. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 78, wherein said non-session message scope types comprise a non-session message scope type of "File". 80. The apparatus for scoped message switching between a sender process and a plurality of receiver processes as set forth in Claim 79- wherein said shared joined list for said non-session message scope type equaling "File" comprises a plurality of shared joined sub-lists, shared among said switches joined to said non-session message scopes of said non-session message scope type equaling "File", and organized on a per file basis. 81. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 75, wherein said joining means further comprises at least one shared program pending messages queue, where program pending messages comprising message scope type attributes not equaling "Session"s are queued. 82. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 81, wherein said non-session program pending messages queues further comprise a plurality of shared lists, shared among said switches joined to said message scope types not equaling "Session"s, organized on a per message scope type basis. 83. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 82, wherem said non-session shared lists comprise a list for one of said non- session message scope types equaling "File". 84. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 82, wherein said "File" scoped shared list comprises a plurality of shared sub-lists, shared among said switches joined to non-session message scopes of said non-session message scope type equaling "File", organized on a per file basis. 85. The apparatus for scoped message switching between a sender process and a plurality of receiver processes as set forth in Claim 75, wherem each of said substantially identical interprocess message switches comprises a first registering means for registering said receiver processes with said switch, said registering means comprising a first interface for receiving registrations, said receiver processes being local receiver processes of said switch; a first selecting means for selecting said registered local receiver processes and said joined switches to receive scoped messages received from said sender process and said joined switches, said first selecting means comprising a second interface for receiving scoped messages from said sender process and said joined switches, said sender process being local sender process of said switch; a first queuing means coupled to said first selecting means for queuing said received scoped messages with selected local receiver processes and said received scoped messages with selected joined switches; a first signaling means coupled to said first queuing means for signaling said selected local receiver processes regarding availability of said queued scoped messages; and a first delivering means for delivering said queued scoped messages, upon request of said signaled local receiver processes, to said requesting local receiver processes, said first delivering means comprising a third interface for receiving said delivery request. 86. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 85, wherein said first interface for receiving registration receives said registrations from said registering local receiver processes dynamically at their initialization and during their execution. 87. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 86, wherein said first registering means for registering said receiver processes comprises a first processing means coupled to said first interface for processing one of said received registrations comprising signaling ways, said signaling ways describing how said registering local receiver process is to be signaled regarding availability of said queued scoped messages for said registering local receiver process, said first processing means storing said signaling ways into tables. 88. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 87, wherein said first registering means for registering said receiver processes further comprises a second processing means coupled to said first interface for processing one of said received registrations comprising message patterns, said second processing means storing said message patterns into said tables, said message patterns comprising a plurality of message attributes describing said scoped messages which said registering local receiver process is to receive, said message attributes comprising a message scope type attribute. 89. The apparatus for scoped interprocess message switching between a sender process and a plurality of processes as set forth in Claim 88, wherein said first registering means for registering said receiver processes further comprises a third processing means coupled to said first interface for processing one of said received registrations comprising a program type identifier, said program type identifier identifying a program being executed by said registering local receiver process, said third processing means generating said message patterns for said registering local receiver process, using message signatures contained within a stored program type definition comprising a matching program type identifier, and storing said message patterns into said tables. 90. The apparatus for scoped interprocess message switching between a sender process and a plurality of processes as set forth in Claim 89, wherein each of said stored program type definitions further comprises a set of start up parameters and at least one of said message signatures, each of said message signatures comprising one of said message patterns and a message disposition attribute. 91. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 90 wherein said first, second and third processing means for processing said received registrations further comprise means for adding said registrations. 92. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 91, wherein said first, second and third processing means for processing said received registrations further comprise means for deleting said registrations. 93. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 92, wherein said means for adding and deleting registrations further comprise means for adding and deleting subsets of said registrations, said subsets comprising message non-session scope identifier attributes, said non-session scope identifiers comprising file identifiers. 94. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 85, wherein each of said messages received from said sender process comprises, an identifier for said received scoped message comprising a sender computer identifier, a sender process identifier and a sender process specific message identifier; a message scope type attribute comprising one of a plurality of message scope types, said message scope types comprising a scope type of "Session", a scope type of "File", a scope type of "File in Session" and a scope type of "File or Session"; a message sender session identifier attribute comprising a session identifier; a message recipient attribute comprising one of a plurality of recipient specifications, said recipient specifications comprising a recipient specification of "Handler Only", a recipient specification of "Observer Only" and a recipient specification of "Both Handler and Observers"; and a message dispatched list attribute comprising a plurality of dispatched records, each of said dispatched records comprising a session identifier for one of said switches, and a timestamp. 95. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 94, wherein said message attributes in some of said received scoped messages further comprise a message non-session scope identifier attribute comprising one of a plurality of non-session message scope identifiers, said non-session message scope identifiers comprising file identifiers. 96. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 94, wherein said message attributes in some of said received scoped messages further comprise a message class attribute, each of said message classes being one of a plurality of message classes comprising a message class of "Request" and a message class of "Notice". 97. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 94, wherein said message attributes in some of said received scoped messages further comprise a message state attribute, each of said message states being one of a plurality of message states comprising a state of "Created", a state of "Sent", a state of "Handled", a state of "Failed", a state of "Started", and a state of "Queued". 98. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 94, wherein said message attributes in some of said received scoped messages further comprise a message operation attribute and a message argument attribute. 99. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 94, wherein said message attributes in some of said received scoped messages further comprise an identifier for said sender process. 100. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 94, wherein said message attributes in some of said received scoped messages further comprise a program type identifier for said sender process. 101. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 94, wherein said message attributes in some of said received scoped messages further comprise an identifier for a handler process. 102. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Qaim 94, wherein said message attributes in some of said received scoped messages further comprise a program type identifier for said handler process. 103. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 94, wherein said message attributes in some of said received scoped messages further comprise a message disposition attribute, each of said message dispositions being one of a plurality of message dispositions comprising a disposition of "Queue", a disposition of "Start", and a disposition of "Discard", said "Discard" disposition being the default disposition if no disposition is specified. 104. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 94, wherein said message attributes in some of said received scoped messages further comprise a message failure reason attribute. 105. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 85, wherein said first selecting means for selecting said registered local receiver processes and said joined switches selects at most one local handler process for each of said received scoped messages, said first selecting means further selects at most one joined switch for each of said received scoped messages with non-session message scopes when said local handler process is not selected and said non-session scoped messages are received from said local sender process. 106. The apparatus for scoped interprocess message switdiing between a sender process and a plurality of receiver processes as set forth in Qaim 105, wherein said local handler processes and joined switches are selected for said received scoped messages having message redpient attributes equaling "Both Handler and Observers" as well as equaling "Handler Only", and message class attributes equaling M Notice"s as well as equaling "Request's. 107. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Qaim 105, wherein said first selecting means for selecting said registered receiver processes and said joined means further selects any number of local observer processes for each of said received scoped messages, said first selecting means further selects any number of joined switches for each of said received scoped messages with non-session message scopes when said non-session scoped messages are received from said local sender process. 108. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Qaim 107, wherein said local observer processes and joined switches are selected for said received scoped messages having message redpient attributes equaling "Both Handler and Observers" as well as equaling "Observers Only", and message dass attributes equaling "Request's as well as equaling "Notice"s. 109. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Qaim 107, wherein said local handler and observer processes being selected comprises non-executing as well as executing local handler and observer processes. 110. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Claim 85, wherein said first selecting means for sdecting said registered local receiver processes and said joined switches comprises a first matching means coupled to said second interface for matching message attributes in said received scoped messages against message attributes in message patterns registered by said local receiver processes, said message patterns being stored in tables accessible to said first matching means. 111. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Qaim 110, wherein said first selecting means for selecting said registered local receiver processes and said joined switches further comprises, a second matching means coupled to said first matching means for matching said message attributes in said received scoped messages against said message attributes in said message patterns contained in message signatures, said message signatures being contained in stored program type definitions, said program type definitions being stored in files accessible to said second matching means; and a third matching means coupled to said second matching means for matching program type identifiers contained in said stored program type definitions having said matching message attributes, against program type identifiers of programs being executed by said registered receiver processes. said program type identifiers being stored in tables accessible to said third matching means; said matching against message signatures and against program type identifiers being performed when said received scoped messages being received from said local sender process. 112. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Qaim 111, wherein said first selecting means for sdecting said local registered receiver processes and said joined switches further comprises a choosing means coupled to said third matching means for choosing one local handler process by ranking said matching message attributes of said matching message patterns and said matching message signatures, said choosing means chooses said one local handler process arbitrarily if said rankings of said matched message attributes are tied. 113. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Qaim 112, wherein said first selecting means for sdecting said local registered receiver processes and said joined switches further comprises a starting means coupled to said choosing means for starting said local receiver processes, said local receiver processes being started comprise said local receiver processes executing said programs identified by said stored program type definitions with said matching message signatures, said programs not -being executed by other registered receiver processes, said matching message signatures comprising message disposition attributes of "Start". 114. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 113, wherein said first sdecting means for sdecting said local receiver processes and said joined switches further comprises a checking means coupled to said third matching means for selecting any number of said joined switches that have not been sent said recdved scoped messages, for each of said recdved scoped message, for remote observer processes selection, said checking means sdects said joined switches by checking joined records in joined lists of said joining means; said checking means further updates message attributes of said recdved scoped messages and sends said updated scoped messages to said sdected joined switches, said updates comprising updating message redpient attributes to "Observers Only's and message dispatched list attributes with sessions identifiers of said selected joined switches; said selections of joined switches for remote observer processes selection being performed when said recdved scoped messages are scoped to non-session message scopes and recdved from said local sender process. 115. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Qaim 114, wherein said checking means further arbitrarily sdects one of said joined " switches that have not been sent said recdved scoped messages, for each of said recdved scoped messages for remote handler process sdection; said checking means further updates said message attributes of said recdved scoped messages and sends said updated scoped messages to said selected joined switches, said updates comprising updating message redpient attributes to "Handlers Only"s, message handler's program type attributes with handler program types from matching message signatures and message dispatched list attributes with sessions identifiers of said sdected joined switches; said selections of a joined switch for remote handler process sdection being performed when said recdved scoped messages are scoped to non- session message scopes, said non-session scoped messages being recdved from said local sender process and local handler processes are not sdected. 116. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 115, wherein said sdection of one joined switch for remote handler process sdection, for each of said non-session scoped messages received from said local sender process and having no local handler process sdected, is repeated until a remote handler process is sdected by one of said selected joined switches or all of said eligible joined switches have been sdected. 117. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 85, wherein said first queuing means for queuing copies of said recdved scoped messages with sdected local recdver processes queues copies of said recdved scoped messages into at least one undelivered messages queue for subsequent retrieval by said selected local recdver processes. 118. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 117, wherein said undelivered messages queues comprise a plurality of private lists, organized on a per process basis. 119. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 117, wherein said first queuing means for queuing copies of said recdved scoped messages with sdected local recdver processes further queues copies of said recdved scoped messages into at least one process pending messages queue, for subsequent retrieval by said selected local recdver processes, said received scoped messages with sdected local receiver processes having their copies queued into said program pending messages queues comprise said received scoped messages comprising session message scopes, message attributes matching against message signatures, said matching message signatures further comprising message disposition attributes equaling "Queue"s, and being contained in program type definitions identifying programs not being executed by said registered local recdver processes. 120. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 119, wherein said program pending messages queues comprise a plurality of private lists, organized on a per program type identifier basis, where said program pending messages comprising message scope type attributes equaling "Session's are queued. 121. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 117, wherein said first queuing means for queuing copies of said recdved scoped messages with selected sdected joined switches further queues copies of said recdved scoped messages with sdected joined switches into at least one results pending messages queue. 122. The method for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 121, wherein said results pending messages queues comprise a plurality of private lists, organized on a per process basis. 123. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Claim 85, wherein said first signaling means for signaling said sdected local receiver processes, signals said selected local recdver processes by posting events for said sdected local recdver processes to detect using system event detection services. 124. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 85, wherein said first delivering means for delivering said queued scoped messages for said selected local recdver processes, dequeues said queued scoped messages from messages queues and sends said dequeued scoped messages to said sdected local recdver processes , using system message sending services, said messages queues being accessible to said first delivering means. 125. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Claim 85, wherein said apparatus further comprises a first updating means coupled to said first sdecting means for discarding said recdved scoped "Notice" messages; said received "Notice" messages comprising scoped "Notice" messages with no sdected local recdver processes and no joined switches for selection of remote receiver processes. 126. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 125, wherein said recdved scoped "Notice" messages with no sdected local receiver processes and no joined switch for sdection of remote receiver processes comprise said recdved scoped "Notice" messages having message attributes non-matching against registered message patterns and non- matching against message signatures contained in program type definitions; said non-matching scoped "Notice" messages having non-session message scopes further having no joined switches that have not been sent said non-matching scoped "Notice" messages. 127. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 126, wherein said recdved scoped "Notice" messages with no sdected local recdver processes and no selected joined switches for sdection of remote receiver processes further comprise said received scoped "Notice" messages having said message attributes matching against said message signatures, said matching message signatures further comprising message dispositions equaling "Discard"s, and being contained in said program types identifying programs not being executed by said registered receiver processes; said discarding scoped "Notice" messages having non-session message scopes further having no joined switches that have not been sent said non- matching scoped "Notice" messages. 128. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 125, wherein said apparatus further comprise a replying means coupled to said first selecting means for replying to said recdved scoped "Notice" messages, when said scoped "Notice" messages are received from said joined switches. 129. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 128, wherein said replying means comprises a generating means coupled to said first sdecting means for generating and sending said reply messages; said generating means comprising an updating means coupled to said first sdecting means for dequeuing said results pending scoped "Notice" messages from results pending messages queues, generating reply messages by updating said scoped "Notice" messages, and sending said generated reply messages said joined switches from which said scoped "Notice" messages are recdved, said results pending messages queues being accessible to said updating means; said updating comprising updating message state attributes to "Handled"s when local handler processes are selected for said scoped "Notice" messages. 130. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Claim 85, wherein each of said switches further comprises a second registering means for registering said local sender process with said switch, said second registering means comprising a fourth interface for receiving registrations from said local sender process; and a replying means coupled to said first selecting means for replying to said received scoped messages with message dass attributes equaling "Requesf's. 131. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Qaim 130, wherein said second registering means for registering said local sender processes comprises the first registering means for registering signaling ways for said local receiver processes. 132. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 131, wherein said registrations received from said local sender process comprise at least one signaling way for said local sender process, said signaling ways describing how said registering local sender process is to be signaled regarding the availability of queued reply messages. 133. The apparatus for scoped interprocess message switching between a sender process and a plurality of receiver processes as set forth in Qaim 130, wherein said replying means for replying to said recdved scoped "Request" messages replies to said "Request" messages with no selected local handler processes and no selected joined switches, said replying being performed when said "Request" messages with no sdected local handler processes and no sdected joined switches are recdved from said local sender process. 134. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 133, wherein said received scoped "Request" messages with no sdected handler processes and no selected joined switches comprise said recdved scoped "Request" messages having message attributes non-matching against registered message patterns and non-matching against message signatures contained in program type definitions; said recdved non-matching scoped "Request" messages having non- session message scopes further having no joined switches that have not been sent said non-matching scoped "Request" messages. 135. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 134, wherein said recdved scoped "Request" messages with no sdected handler processes and no sdected joined switches further comprise said received scoped "Request" messages having said message attributes matching against said message signatures, said matching message signatures further comprising message dispositions equaling "Discard"s, and being contained in said program types identifying programs not being executed by said registered receiver processes; said discarding scoped "Request" messages having non-session message scopes further having no joined switches that have not been sent said non-matching scoped "Request" messages. 136. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 133, wherein said replying means for replying to said recdved scoped "Request" messages further replies to said "Request" messages with selected local handler processes and said "Request" messages with handler selecting joined switches; said replying being performed when said "Request" messages with sdected handler processes and said "Request" messages with handler sdecting joined switches are received from said local sender processes. 137. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 130, wherein said replying means for replying to said recdved scoped "Request" messages comprises, a generating means coupled to said first selecting means for generating reply messages to said received scoped "Request" messages; a second sdecting means coupled to said generating means for sdecting said registered local recdved processes and said joined switches to recdve said reply messages; a second queuing means coupled to said second sdecting means for queuing said reply messages, for subsequent retrieval by said local sender process and said sdected local receiver processes; a second signaling means coupled to said second registering means and said second queuing means for signaling said local sender process and said sdected local recdver processes regarding the availability of said queued reply messages; and a second delivering means for delivering said queued reply messages, upon request of said signaled local processes, to said requesting local processes, said delivering means comprising a fifth interface for recdving said delivery requests. 138. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 137, wherein said generating means for generating reply messages comprises an updating means coupled to said first sdecting means for updating message attributes of said recdved scoped "Request" messages with no selected handler process and no selected joined switches, said message attributes being updated comprising message state attributes being updated to "Failed"; said updating being performed when said scoped "Request" messages with no sdected handler processes and no sdected joined switches are recdved from said local sender process. 139. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 138, wherein said updating means further updates message attributes of said recdved scoped "Request" messages with sdected handler processes and said received scoped "request" messages with sdected joined switches, said message attributes being updated according to handling results received, said handling results received comprising handling results recdved from local handler processes and remote handler sdecting joined switches, and said message attributes being updated comprising message state attributes being updated to one of a plurality of message states comprising a state of "Handled" and a state of "Failed"; said updating being performed when said scoped "Request" messages with sdected local handler processes and said scoped "Request" messages with sdected joined switches are recdved from said local sender process. 140. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 139, wherein said generating means for generating reply messages further comprises a third queuing means coupled to said first selecting means for queuing another copy of each of said received scoped "Request" messages with sdected local handler processes, pending recdpt of said results from said local handler processes. 141. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 140, wherein said third queuing means for queuing copies of said received scoped "Request" messages with selected handler processes, queues said copies into at least one results pending messages queues. 142. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 141, wherein said results pending messages queues comprise a plurality of private lists, organized on a per process basis; said results pending message queues being the same results pending messages queues for queuing said received scoped messages with sdected joined switches for remote handler processes sdection. 143. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 142, wherein said replying means comprises the same replying means for replying to scoped "Notice" messages; said generating means comprising the same generating means of said replying means for replying to scoped "Notice" messages; said second updating means comprising the same updating means of said generating means of said replying means for replying to scoped "Notice" messages; and said third queuing means comprising said first queuing means. 144. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 137, wherein said second selecting means for selecting said registered local recdver processes and said joined switches for said reply messages selects any number of local observer processes; said second selecting means further sdects any number of said joined switches for remote observer processes selection when said reply messages are scoped to non-session message scopes. 145. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 144, wherein said second selecting means for selecting local observer processes and said joined switches comprises the first sdecting means for selecting said registered local recdver processes and said joined switches for said recdved scoped messages from said sender process. 146. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 137, wherein said second queuing means for queuing copies of said reply messages for said local sender process and said sdected local observer processes comprises said first queuing means for queuing copies of the said received scoped messages with selected local recdver processes and copies of said recdved scoped messages with selected joined switches. 147. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 137, wherein said second signaling means for signaling said local sender process and said sdected local recdver processes for said reply messages comprises said first signaling means for signaling said sdected local recdver processes regarding the availability of said queued messages received from said local sender process. 148. The apparatus for scoped interprocess message switching between a sender process and a plurality of recdver processes as set forth in Qaim 137, wherein said second delivering means for delivering said queued reply messages comprises said first delivering means for delivering said queued messages recdved from said local sender process. 149. A method for interprocess message switching between a sender and a plurality of recdver processes, said method comprising the steps of. a) registering each of said recdver processes; b) selecting said registered recdver processes to receive messages recdved from said sender process; c) queuing copies of said recdved messages with selected recdver processes; d) signaling said sdected recdver processes regarding the availability of said queued messages; and e) delivering said queued messages upon request of said signaled recdver processes to said requesting recdver processes. 150. The method as set forth in daim 149, wherein said messages are scoped messages. 151. The method as set forth in daim 149, wherein said messages are process oriented messages. 152. The method as set forth in daim 149, wherein said messages are object oriented messages. 153. An apparatus for interprocess message switching between a sender and a plurality of recdver processes, said apparatus comprising: a) at least one registering means for registering each of said recdver processes; b) at least one selecting means coupled to said at least one registering means for sdecting said registered receiver processes to receive messages received from said sender process; c) at least one queuing means coupled to said at least sdecting means for queuing copies of said recdved messages with sdected recdver processes; d) at least one signaling means coupled to said at least one registering means for signaling said selected recdver processes regarding the availability of said queued messages; and e) at least one delivering means coupled to queuing means for delivering said queued messages upon request of said signaled receiver processes to said requesting receiver processes. 154. The apparatus as set forth in daim 153, wherein said messages are scoped messages. 155. The apparatus as set forth in daim 153, wherein said messages are process oriented messages. 156. The apparatus as set forth in daim 153, wherein said messages are object oriented messages.

Inventors: FOSS CAROLYN L, HARE DWIGHT F, MCALLISTER RICHARD F, NGUYEN TIN ANH, PEARL AMY, SHAIO SAMI, FOSS, CAROLYN, L., HARE, DWIGHT, F., MCALLISTER, RICHARD, F., NGUYEN, TIN, ANH, PEARL, AMY, SHAIO, SAMI
Applicants: SUN MICROSYSTEMS INC, SUN MICROSYSTEMS, INC.
Application year: 1992
Main classification: G06F15
IPC codes: G06F9, G06F13, G06F15