System and method of providing inter-application communications

Abstract

A method of operating an operating system for providing inter-application communications between a publisher application and a subscriber application. The method includes receiving a publication request from the publisher application at an operating system, receiving a subscriber application from the subscriber application at the operating system, performing an operating system based event brokering procedure based on the publication request and the subscription request, and publishing an event based on the procedure.

Description

SUMMARY

One form of the present invention is a data processing system, computer program product and/or method of operating an operating system for providing inter-application communications between a publisher application and a server application. The method includes receiving a publication request from the publisher application at the operating system, receiving a subscription request from the subscriber application at the operating system, performing an operating system based event brokering procedure based on the publication request and the subscription request, and publishing an event based on the procedure.

A second form of the present invention is an operating system for providing inter-application communications between a publisher application and a subscriber application. The operating system comprises computer readable code for receiving a publication request from the publisher application at the operating system, computer readable code for receiving a subscription request from the subscriber application at the operating system, computer readable code for performing an operating system based event brokering procedure based on the publication request and the subscription request, and computer readable code for publishing an event based on the procedure.

A third form of the present invention is an operating system for providing inter-application communications between a publisher application and a subscriber application. The operating system comprises means for receiving a publication request from the publisher application at the operating system, means for receiving a subscription request from the subscriber application at the operating system, and means for performing an operating system based event brokering procedure based on the publication request and the subscription request, and means for publishing an event based on the procedure.

The foregoing and other features and advantages of the invention will become further apparent from the following detailed description of the presently preferred embodiments, read in conjunction with the accompanying drawings. The detailed description and drawings are merely illustrative of the invention, rather than limiting the scope of the invention being defined by the appended claims and equivalents thereof.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system for controlling copying of documents, in accordance with one embodiment of the present invention;

FIG. 2 illustrates a flow chart of providing inter-application communications in accordance with one embodiment of the present invention;

FIG. 3 illustrates communications between two applications through an operating system, in accordance with one embodiment of the present invention; and

FIG. 4 illustrates a registry of an operating system, in accordance with one embodiment of the present invention.

DETAILED DESCRIPTION

FIG. 1 illustrates one embodiment of a computer client 150 for use in accordance with one aspect of the invention. Computer system 150 employs a peripheral component interconnect (PCI) local bus architecture. Although the depicted example employs a PCI bus, other bus architectures such as Micro Channel and ISA can be used. PCI bridge 158 connects processor 152 and main memory 154 to PCI local bus 156. PCI bridge 158 also can include an integrated memory controller and cache memory for processor 152. Additional connections to PCI local bus 156 can be made through direct component interconnection or through add-in boards. In the depicted example, local area network (LAN) adapter 160, SCSI host bus adapter 162, and expansion bus interface 164 are connected to PCI local bus 156 by direct component connection. In contrast, audio adapter 166, graphics adapter 168, and audio/video adapter (A/V) 869 are connected to PCI local bus 156 by add-in boards inserted into expansion slots. Expansion bus interface 164 connects a keyboard and mouse adapter 170, modem 172, and additional memory 174 to bus 156. SCSI host bus adapter 162 provides a connection for hard disk drive 176, tape drive 178, and CD-ROM 180 in the depicted example. In one embodiment, the PCI local bus implementation support three or four PCI expansion slots or add-in connectors, although any number of PCI expansion slots or add-in connectors can be used to practice the invention.

An operating system runs on processor 152 to coordinate and provide control of various components within computer system 150. Further, the operating system coordinates inter-application communications as described in further detail below. The operating system can be any appropriate available operating system such as Windows, Macintosh, UNIX, AIX, HP-UX, LINUX, or OS/2, or the like. “Windows” is a trademark of Microsoft Corporation. “Macintosh” is a trademark of Apple Computer, Inc. “UNIX” is a trademark of The Open Group. HP-UX is a trademark of Hewlett-Packard Company. “Linux” is a trademark of the Linux Mark Institute. “A/X” and “OS/2” are trademarks of International Business Machines Corporation. Instructions for the operating system, an object-oriented operating system, and applications or programs are located on storage devices, such as hard disk drive 176 and can be loaded into main memory 154 for execution by processor 152.

Those of ordinary skill in the art will appreciate that the hardware in FIG. 1 may vary depending on the implementation. For example, other peripheral devices, such as optical disk drives and the like may be used in addition to or in place of the hardware depicted in FIG. 1. FIG. 1 does not illustrate any architectural limitations with respect to the present invention, and rather merely discloses an exemplary system that could be used to practice the invention. For example, the processes of the present invention may be applied to two or more client computers connected by a local area network (LAN) or a wide area network (WAN), such as the Internet.

The invention can take the form of an entirely hardware embodiment or an embodiment containing both hardware and software elements. Furthermore, the invention can take the form of a computer program product accessible from a computer-usable or computer-readable storage device providing program code for use by or in connection with one or more computers or any instruction execution system. For the purposes of this description, a computer-usable or computer readable storage device can be any apparatus that can store the program for use by or in connection with the instruction execution system, apparatus, or device. The storage device can be an electronic, magnetic, optical, electromagnetic, or semiconductor system (or apparatus or device). Examples of a computer-readable storage device include a semiconductor or solid-state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. The term “computer-readable storage device” does not encompass a signal propagation media such as a copper transmission cable, an optical transmission fiber or wireless transmission media.

FIG. 2 illustrates one embodiment of a method 200 of providing inter-application communications in accordance with one aspect of the invention. Method 200 begins at step 210. Any of the inventive method steps disclosed herein may be performed in any order, and the order in which the method steps are described does not limit the order in which the steps can be performed. In addition, the method steps and decision therein can be implemented automatically through program coding or through a human user of the computer client.

Method 200 continues at step 220 by receiving a publication request from a publisher application at an operating system (OS). An OS organizes and controls operations of hardware and provides an environment to execute applications on top of and under control of the OS. In one embodiment, the operating system 300 is in communication with a registry repository 310, shown in FIG. 3, for mediating inter-application communications of events 320 between the publisher application 330 and a subscriber application 340. In one embodiment, a filter 350 filters events 320 prior to an interaction between the event listener interface 360 and the events 320. Certain event(s) 322 do not pass through filter 350. An event is defined herein as a representation of an occurrence within an application. An event may be data, such as, for example WL. An event may alternatively be, or include, an executable portion, for example a compiled program or executable code.

As shown in FIG. 4, a registry 400 contains metadata describing events produced by various applications that file a publication request with the operating system. Metadata stored in the registry 400 is structured as a collection of application names 410. An application identifier, such as an individual application name 412, is associated with a schema of event types 420 that it may publish, or is subscribed to. An exemplary schema is illustrated in FIG. 4 and includes four event types 420. In one embodiment, event 420 may include properties for describing the event 420 to a subscribed application. The properties may include information for controlling events on an application subscribed to that particular event, for example mouse position or movement data associated with the control mouse movement event. Event 420 can be, for example, formatted as an XML message.

At step 230, the publisher application is registered with the operating system. In one embodiment, the registration takes place during an installation process. Alternatively, the publisher application registers during an independent registration process. For example, if the publisher application is already installed, the publisher application can register at any point by running the independent registration process. At either of these points, a process is run to register the application, and the events it may publish, with the registry of the operating system. In one embodiment, this registration process may be run independently of installation. For example, another application or a system user can request that the publisher application register if it is not already done so. Post-installation registration or update of registration can be applied in instances of a software update, user request, or other process.

At step 240, a subscription request is received from a subscriber application at the operating system. In one embodiment, the subscription request is recorded at the registry. A subscription request may include an application identifier, such as an application name. The application identifier may indicate which application from which the subscriber application wishes to receive events. When a subscription request is received at the operating system, the application identifier may be compared to a collection of application identifiers that are currently registered as publisher applications.

At step 250, an event filter is created. The subscription request may also include a list of event types or other subscription criteria. Subscription criteria may be used to filter what events are passed to the subscriber application. In one embodiment, the subscriber application creates an event filter with the operating system during the filing of a subscription request. An event filter may specify the number and type of published events that are communicated from the registry to the subscriber application. For example, the event filter may only allow published events of an event type specified in subscription criteria to pass through to the subscriber application. The subscription request may include an object that implements an event listener interface with the operating system. The event listener interface of the operating system waits for detection of published events that pass through the filter. If the event matches the subscription request, and passes one or more event filters if they exist, the listener interface communicates the event to the subscriber application. If the event does not match the subscription request, or does not pass at least one of the event filters, the listener interface does not communicate the event to the subscriber application.

The event filter and an event listener interface facilitate an operating system based event brokering by the operations system that encompasses steps 260, 270 and 280.

At step 260, an event is published upon receiving the publication request at the operating system. A published event is an event that has occurred in an application and has been received by the operating system for brokering. In one embodiment, a published event awaits communication to the subscriber application.

In one embodiment, the publisher application publishes and stores events in the registry repository at step 270. Information may be alternatively stored in a standard file or database. The registry repository is a system-defined database used by the operating system to store configuration information. Applications may register, write data and publish events, all of which may be stored and retrieved through the registry repository. The data and format of the registration and published events in the registry and registry repository can vary according to the version and brand of the operating system, or according to the implementation of the operating system event brokering. The operating system may provide publication of the events stored in the registry repository for times the subscriber application is unavailable (e.g., not running). For example, if the subscriber application is closed when an event is published, the published events may be communicated to the subscriber application when it becomes active, as the events have been stored in the registry repository. Alternatively, published events may be discarded if the subscriber application is not available to provide real-time publication and subsequent communication of the event.

Those skilled in the art will recognize that the publisher and subscriber applications can vary in number. For example, a single publisher application can communicate with a plurality of subscriber applications. Likewise, a single subscriber application can communicate with a plurality of publisher applications. The invention is not limited to a single publisher application and a single subscriber application. For example, a plurality of computers running the subscriber application can subscribe for another computer running the publisher application through a connection. As such, published publisher application events are broadcast to numerous computers running the subscriber application through the Internet. As another example, a single subscriber application subscribes to events published by numerous publisher applications running on the same computer. As such, the subscriber application utilizes the information of the events of the numerous publisher applications for various purposes.

At step 280, the published event is communicated from the operating system to the subscriber application based on the subscription request. In one embodiment, the published event is communicated from the operating system registry repository to a subscriber application running on the same client computer as the publisher application. In another embodiment, the published event is communicated from the registry repository to one or more instances of the subscriber application running on separate client computer(s) and linked through a LAN or WAN, such as the Internet. Communication involves sending the published event from the registry repository of the OS of the publisher application to the subscriber application via a network connection. The published event may cause the subscriber application to perform some action. In one embodiment, the event may include a compiled program or application code, either of which may cause the subscriber application to perform some action. For example, a published event can control certain characteristics of the subscriber applications (e.g., mouse movements and/or clicks, open and closing the subscriber application, publication/display of data in real-time, and the like).

As the events are published through the operating system, programming code for providing direct inter-application communication capabilities is not required for each individual application. In addition, the use of an operating system as an event broker can reduce incompatibility issues as the strategy for communicating between applications is standardized. Besides providing an event filter and event listener, the operating system can provide event logging, guaranteed event delivery, event correlation, protocol translation, and other functions.

Those skilled in the art will appreciate that the publisher and subscriber applications can exchange published events through the operating system in a bilateral manner. For example, the subscriber program optionally includes capabilities of the publisher program whereby the program publishes events to the registry repository. The publisher program, which optionally includes capabilities of the subscriber program, subscribes to the events. The publisher and subscriber programs can exchange information in a synchronous or asynchronous manner on the same computer or over different client computers over a LAN or WAN. In this manner, applications may be run over multiple computers in a distributed manner via a publish/subscribe mechanism over the Internet.

In one embodiment, information can be shared during a network meeting, which illustrates various steps implemented by the present invention. A publisher application, running on a host computer, publishes screen shot images as well as various actions being performed on the application. These events may be published over a network (e.g., Internet) to numerous participants (e.g., client computers) in the meeting. The participants each run the subscriber application, which receives published events (i.e., as screen shot images and the actions) from the OS of the publisher computer based on subscription requests from the subscriber application at step 240. The participants can see not only the screen shot images being communicated across the network, but also the actions being performed on the publisher application as step 280. Processing may terminate thereafter at step 290.

In the present example, the published events (e.g., which are subscribed to during step 250) are communicated from the publisher application to the subscriber application via the OS of the host computer, which were stored in the registry repository during step 240. The published events (which are published during step 270) include the screen shot images as well as the actual actions being performed on the publisher application. As such, the network meeting allows communication between the publisher application and OS run on the host computer and the subscriber application run on the client computer(s).

In one embodiment, the publisher/subscriber model may be applied to hand writing recognition. For example, some hand writing recognition software applications have two modes, one for recognizing alphabetical characters and the other for recognizing numeric characters. The handwriting and numeric applications can subscribe to another application for providing, for instance, contacts, calendars, appointments, and the like. When a user tabs to a numeric field in an appointment application (e.g., the publisher application) the tab information can be communicated as published events to the handwriting recognition application (e.g., the subscriber application). The handwriting recognition application can then automatically switch its mode to the numeric recognition application. As such, communication is provided between a publisher application, OS, and subscriber application running on the same computer.

While the embodiments of the present invention disclosed herein are presently considered to be preferred embodiments, various changes and modifications can be made without departing from the spirit and scope of the present invention. The scope of the invention is indicated in the appended claims, and all changes that come within the meaning and range of equivalents are intended to be embraced therein.

Claims

1. A method of sharing information entered by a publisher application to a participant, the method comprising: receiving a subscription request from a subscriber application of the participant that specifies the publisher application and subsequently, the subscriber application becoming inactive, and subsequently setting up an event filter to specify events subscribed-to as limited to an event type;receiving a published event from the publisher application, the published event representing an action performed by the publisher application on a user interface, the published event comprising action program code to perform the action on the user interface, and in response, to the published event, one or more processors determining that the published event matches the subscription request from the subscriber application while the subscriber application is inactive, and subsequently, the one or more processors determining that the subscriber application becomes active, and only in response,sending a screen shot of the user interface from an operating system of the publisher application to the subscriber application;sending the action, including the action program code, separate from the screen shot, from the operating system of the publisher application to the subscriber application; andthe subscriber application receiving and displaying the screen shot, receiving the action program code and subsequently executing the action program code to perform the action and displaying a result of the execution of the action program code on the screen shot such that the participant sees the action performed on the user interface after seeing the user interface before the action was performed;receiving a second subscription request from a second subscriber application of a second participant that specifies a publisher application and subsequently, the second subscriber application becoming inactive; andsubsequent to receiving the second subscription request from the second subscriber application of the second participant that specifies the publisher application of the publisher, setting up a second event filter to specify events subscribed-to as limited to the event type, wherein the event type comprises mouse position.

2. The method of claim 1, wherein setting up an event filter comprises setting up an event listener interface to establish criteria to prevent an event reaching the subscriber application.

3. The method of claim 1, wherein the published event comprises an XML message event type.

4. A computer program product for sharing information by a publisher application to a participant, the computer program product comprising: one or more computer-readable storage devices and program instructions, stored on at least one of the one or more storage devices, the program instructions comprising:program instructions to receive a subscription request from a subscriber application of the participant that specifies the publisher application and subsequently, the subscriber application becoming inactive;program instructions to receive a published event from the publisher application, the published event representing an action performed by the publisher application on a user interface, the published event comprising action program code to perform the action on the user interface, and in response, to the published event, determine that the published event matches the subscription request from the subscriber application while the subscriber application is inactive, and subsequently, determine that the subscriber application becomes active, and only in response, send a screen shot of the user interface from an operating system of the publisher application to the subscriber application;program instructions to send the action, including the action program code, separate from the screen shot, from the operating system of the publisher application to the subscriber application;program instructions to receive the action program code and display the screen shot, and subsequently execute the action program code to perform the action and display a result of the execution of the action program code on the screen shot such that the participant sees the action performed on the user interface after seeing the user interface before the action was performed;program instructions to receive a second subscription request from a second subscriber application of a second participant that specifies a publisher application and subsequently, the second subscriber application becoming inactive; andprogram instructions to set up a second event filter to specify events subscribed-to as limited to the event type, subsequent to receiving the second subscription request from the second subscriber application of the second participant that specifies the publisher application of the publisher, wherein the event type comprises mouse position.

5. The computer program product of claim 4, wherein program instructions to set up an event filter comprises program instructions to set up an event listener interface to establish criteria to prevent an event reaching the subscriber application.

6. The computer program product of claim 4, wherein the published event comprises an XML, message event type.

7. A computer system for sharing information entered by a publisher application to a participant, the computer system comprising: one or more processors, one or more computer-readable memories, one or more computer-readable storage devices and program instructions, stored on the one or more storage devices for execution by the one or more processors via the one or more memories, the program instructions comprising:program instructions to receive a subscription request from a subscriber application of the participant that specifies the publisher application and subsequently, the subscriber application becoming inactive;program instructions to receive a published event from the publisher application, the published event representing an action performed by the publisher application on a user interface, the published event comprising action program code to perform the action on the user interface, and in response, to the published event, determine that the published event matches the subscription request from the subscriber application while the subscriber application is inactive, and subsequently, determine that the subscriber application becomes active, and only in response, send a screen shot of the user interface from an operating system of the publisher application to the subscriber application;program instructions to send the action, including the action program code, separate from the screen shot, from the operating system of the publisher application to the subscriber application;program instructions to receive the action program code and display the screen shot, and subsequently execute the action program code to perform the action and display a result of the execution of the action program code on the screen shot such that the participant sees the action performed on the user interface after seeing the user interface before the action was performed;program instructions to receive a second subscription request from a second subscriber application of a second participant that specifies a publisher application and subsequently, the second subscriber application becoming inactive; andprogram instructions to set up a second event filter to specify events subscribed-to as limited to the event type, subsequent to receiving the second subscription request from the second subscriber application of the second participant that specifies the publisher application of the publisher.

8. The computer system of claim 7, wherein program instructions to set up an event filter comprise program instructions to set up an event listener interface to establish criteria to prevent an event reaching the subscriber application.

9. The computer system of claim 7, wherein the published event comprises an XML message event type.