Distributed framework for intertask communication between workstation applications

A method of communicating between workstation client applications, comprising the steps of:

• (a) expressing, by a first client non-server application, an interest in a first event by transmitting a first interest object from said first client non-server application to a server,
• said server being operatively interposed between said first client non-server application and a second client non-server application and a third client non-server application,
• said first client non-server application storing therein a first set of stored data, said first set of stored data including a plurality of events, a plurality of interest objects corresponding, respectively, to said plurality of events, and a plurality of functions corresponding, respectively, to said plurality of events and to said plurality of interest objects, said first client non-server application further including an open state status icon and a closed state status icon,
• said second client non-server application storing therein a second set of stored data, said second set of stored data including a plurality of events, a plurality of interest objects corresponding, respectively, to said plurality of events, and a plurality of functions corresponding, respectively, to said plurality of events and to said plurality of interest objects, said second client non-server application further including an open state status icon and a closed state status icon,
• said third client non-server application storing therein a third set of stored data, said third set of stored data including a plurality of events, a plurality of interest objects corresponding, respectively, to said plurality of events, and a plurality of functions corresponding, respectively, to said plurality of events and to said plurality of interest objects, said third client non-server application further including an open state status icon and a closed state status icon;
• (b) receiving said first interest object in said server and retransmitting by said server, said first interest object to said second client non-server application and to said third client non-server application;
• (c) comparing, by said second client non-server application, said first interest object received from said server with the plurality of interest objects in said second set of stored data stored in said second client non-server application;
• (d) comparing, by said third client non-server application, said first interest object received from said server with the plurality of interest objects in said third set of stored data stored in said third client non-server application;
• (e) locating, by said second client non-server application, a match between said first interest object received from said server and one of the interest objects in said second set of stored data stored in said second client non-server application;
• (f) identifying, by said second client non-server application, one of the plurality of events representing said first event in said second set of stored data corresponding to said one of the interest objects in said second set of stored data;
• (g) determining, by said second client non-server application, a state of said second open state status icon and said second closed state status icon;
• (h) transmitting, by said second client non-server application, second event information corresponding to said one of the plurality of events representing said first event in said second set of stored data directly to said first client non-server application without routing said second event information through said server when said second client non-server application practices said one of the plurality of events and when said second open state status icon of said second client non-server application is actuated;
• (i) not transmitting, by said second client non-server application, said second event information directly to said first client non-server application even though said second client non-server application practices said one of the plurality of events when said second closed state status icon of said second client non-server application is actuated;
• (j) receiving, by said first client non-server application, said second event information associated with said one of the plurality of events from said second client non-server application when said second client non-server application practices said one of the plurality of events and when said second open state status icon of said second client non-server application is actuated and when said first open state status icon of said first client non-server application is actuated;
• (k) not receiving, by said first client non-server application, said second event information from said second client non-server application even though said second client non-server application practices said one of the plurality of events and even though said second open state status icon of said second client non-server application is actuated when said first closed state status icon of said first client non-server application is actuated,
• (l) when said first client non-server application receives said second event information associated with said one of the plurality of events from said second client non-server application, comparing, by said first client non-server application, said second event information received from said second client non-server application with the plurality of events in said first set of stored data and locating a match between said second event information and one of the plurality of events in said first set of stored data,
• (m) identifying, by said first client non-server application, one of the plurality of functions in said first set of stored data which corresponds to said one of the plurality of events in said first set of stored data, and
• (n) executing, by said first client non-server application, said one of the plurality of functions.

A method of communicating between client applications, comprising the steps of:

• (a) transmitting an interest object associated with an event from a first client non-server application to a server,
• (b) receiving the interest object in the server and retransmitting the interest object from the server to a second client non-server application;
• and
• (c) when the second client non-server application practices the event, transmitting event information associated with the practice of said event from said second client non-server application directly to said first client non-server application without routing said event information through the server.

A system adapted for intercommunicating between client applications, comprising:

• a first client non-server application adapted to transmit an interest object corresponding to an event;
• a second client non-server application;
• and
• a server operatively interposed between said first client non-server application and said second client non-server application,
• said first client non-server application transmitting said interest object to said server,
• said server transmitting said interest object to said second client non-server application,
• said second client non-server application transmitting said event directly to said first client non-server application without routing said event through said server in response to said interest object received by said second client non-server application from said server when said second client non-server application practices said event.

A method of intercommunicating between client applications, comprising the steps of:

• (a) transmitting a first interest object associated with a first event from a first client non-server application to a server, said first interest object being transmitted from said first client non-server application to said server when said first client non-server application is interested in receiving event information associated with a practice of said first event by other client applications;
• (b) routing said first interest object from said first client non-server application through said server and retransmitting said first interest object from said server to a second client non-server application;
• (c) responding by said server to a revocation object received from said first client non-server application when said first client non-server application transmits said revocation object to said server;
• (d) when said second client non-server application receives said first interest object from said server and when said second client non-server application practices said first event, transmitting event information associated with the practice of said first event from said second client non-server application directly to said first client non-server application, said event information being transmitted directly from said second client non-server application to said first client non-server application without routing said event information through said server;
• and
• (e) when said server receives additional interest objects from other client applications, responding by said server to said additional interest objects received from said other client applications,
• said event information is not transmitted between said second client non-server application and said server, said event information is not transmitted between said server and said first client non-server application,
• said server is not separated from said first client non-server application and said server is not separated from said second client non-server application and said server is not separated from the other client applications when said event information is transmitted from said second client non-server application directly to said first client non-server application, said server remaining operatively interconnected between said first client non-server application and said second client non-server application and the other client applications, when said event information is transmitted from said second client non-server application directly to said first client non-server application, for responding to said revocation object,
• said additional interest objects, and other requests received by the server from the client applications;
• and
• said first client non-server application and said second client non-server application each including icon generating means for generating an icon, and
• event determination means operatively connected to said icon generating means and responsive to user actuation of said icon for determining if all or some or none of said event information is transmitted from said second client non-server application and if all or some of none of said event information is received by said first client non-server application.

An intercommunication system adapted for intercommunicating between client applications, comprising:

• a first client non-server application adapted to transmit an interest object;
• a second client non-server application;
• other client applications adapted to transmit other interest objects;
• and
• a server operatively interposed between said first client non-server application and said second client non-server application and said other client applications,
• said first client non-server application adapted for sending said interest object corresponding to an event to said server,
• said server adapted to receive any revocation objects transmitted from said first client non-server application, said server transmitting said interest object from said server to said second client non-server application,
• said second client non-server application responsive thereto sending event information associated with said event directly to said first client non-server application without routing said event information through said server when said second client non-server application practices said event,
• said server continuing to respond to said other interest objects received from said other additional client applications,
• said event information is not transmitted between said second client non-server application and said server, said event information is not transmitted between said server and said first client non-server application,
• said server is not separated from said fast client non-server application and said server is not separated from said second client non-server application and said server is not separated from said other client applications when said event information is sent from said second client non-server application directly to said fast client non-server application, said server remaining operatively interconnected between said first client non-server application and said second client non-server application and said other client applications when said event information is sent from said second client non-server application directly to said fast client non-server application for responding to said other interest objects, said revocation objects, and other requests from the client applications;
• and
• said first client non-server application and said second client non-server application each including icon generating means for generating an icon, and event determination means operatively connected to said icon generating means and responsive to user actuation of said icon for determining if all or some or none of said event information is transmitted from said second client non-server application and if all or some of none of said event information is received by said first client non-server application.