Processing event notifications with an event sink

• US 8,332,540 B2
• Filed: 06/11/2011
• Issued: 12/11/2012
• Est. Priority Date: 10/25/2007
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Grigsby, Travis M., Lyle, Ruthie D., Seacat, Lisa A.
• Primary Examiner(s): Chan, Wing
• Assistant Examiner(s): WOO, ANDREW M
• Application Number:
  US13/158,374
• Publication Number:
  US 20110239228A1
• Time in Patent Office: 549 Days
• Field of Search: 709/204, 709/227
• US Class Current: 709/250
• CPC Class Codes: G06F 2209/545 Gui
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 51/043 using or handling presence information

Abstract

Applications generating events, and system facilities generating events, send notifications of the events to a system event sink. The event sink is preferably associated with an operating system, and provides an application programming interface for registering listeners. (In one alternative approach, the event sink operates as a centrally-accessible or network-accessible entity, where it may concurrently interact with more than one client.) Upon receiving a notification of an event, the event sink forwards the notification to any registered listeners. Optionally, filters may be used to specify criteria to be met before a notification is forwarded to the listener. An event does not rely on a particular application for displaying the event to an end user. As one example, notification of a newly-arrived e-mail message might be presented in a chat window of an instant messaging client.

Claims

1. A computer-implemented method of processing event notifications, comprising:

generating an event notification, by a first application executing on a client device, responsive to receiving an inbound message at the first application;

sending the generated event notification from the first application to an event sink executing on the client device;

receiving, from the event sink at a second application executing on the client device, the event notification, wherein;

the second application is distinct from the first application;

the second application is registered with the event sink for receiving event notifications pertaining to inbound messages received at the first application; and

the second application is selected by the event sink for rendering the event notification responsive to detecting that a user interface window of the second application currently has focus; and

rendering the received event notification, by the second application, instead of rendering the inbound message by the first application.

2. The method according to claim 1, wherein the generating further comprises inserting a selectable link into the event notification, the selectable link being operable, when the event notification is rendered by the second application, to cause invocation of the first application.

3. The method according to claim 1, wherein the generating further comprises inserting a selectable link into the event notification, the selectable link operable when the event notification is rendered by the second application to cause:

changing the focus on a user interface of the client device from the user interface window of the second application to a user interface window rendered by the first application; and

rendering the inbound message in the user interface window rendered by the first application.

4. The method according to claim 1, wherein the second application is a video player and the rendering comprises visually displaying the received event notification in closed captioning depicted from the video player.

5. The method according to claim 1, wherein the second application is a gaming application and the rendering comprises visually displaying the received event notification as a text message moving across the user interface window of the gaming application.

6. The method according to claim 1, wherein the second application is a screen reader application and the rendering comprises placing text of the received event notification into text of the user interface window from which the screen reader application is currently reading, thereby causing the screen reader application to read the text of the received event notification.

7. The method according to claim 1, wherein:

the first application comprises code that traps message dialogs from a legacy application; and

the generating further comprises translating a particular trapped message dialog into a form usable by the second application.

8. A computer-implemented system for processing event notifications, comprising:

a computer comprising a processor; and

instructions which execute, using the processor, to implement functions comprising;

generating an event notification, by a first application executing on a client device, responsive to receiving an inbound message at the first application;

sending the generated event notification from the first application to an event sink executing on the client device;

receiving, from the event sink at a second application executing on the client device, the event notification, wherein;

the second application is distinct from the first application;

the second application is registered with the event sink for receiving event notifications generated by the first application; and

the second application is selected by the event sink for rendering the event notification responsive to detecting that a user interface window of the second application currently has focus; and

rendering the received event notification, by the second application, instead of rendering the inbound message by the first application.

9. The system according to claim 8, wherein the generating further comprises inserting a selectable link into the event notification, the selectable link being operable, when the event notification is rendered by the second application, to cause invocation of the first application.

10. The system according to claim 8, wherein the generating further comprises inserting a selectable link into the event notification, the selectable link operable when the event notification is rendered by the second application to cause:

changing the focus on a user interface of the client device from the user interface window of the second application to a user interface window rendered by the first application; and

rendering the inbound message in the user interface window rendered by the first application.

11. A computer program product for processing event notifications, the computer program product embodied on at least one non-transitory computer-usable medium and comprising computer-usable program code for:

receiving, at a selected one of a plurality of first applications executing on a client device from an event sink executing on the client device, an event notification, the event notification generated by a second application executing on the client device responsive to receiving an inbound message at the second application and sent from the second application to the event sink, wherein;

the plurality of first applications are registered with the event sink for receiving event notifications pertaining to inbound messages received at the second application, each one of the plurality of first applications being distinct from the second application and from other ones of the first applications; and

the selected one of the first applications is selected by the event sink to receive the event notification according to preferences of a user of the client device; and

rendering the received event notification, by the selected one of the first applications, instead of rendering the inbound message by the second application.

12. The computer program product according to claim 11, wherein the event notification is generated to include a selectable link, the selectable link being operable, when the event notification is rendered by the selected one of the first applications, to cause invocation of the second application.

13. The computer program product according to claim 11, wherein the event notification is generated to include a selectable link, the selectable link operable when the event notification is rendered by the selected one of the first applications to cause:

changing the focus on a user interface of the client device from the user interface window of the selected one of the first applications to a user interface window rendered by the second application; and

rendering the inbound message in the user interface window rendered by the second application.

14. A computer-implemented method of processing event notifications, comprising:

generating an event notification, by a first application executing on a client device, responsive to receiving an inbound message at the first application;

sending the generated event notification from the first application to an event sink executing on the client device;

receiving, from the event sink at a selected one of a plurality of second applications executing on the client device, the event notification, wherein;

the plurality of second applications are registered with the event sink for receiving event notifications pertaining to inbound messages received at the first application, each one of the plurality of second applications being distinct from the first application and from other ones of the second applications; and

the selected second application is selected by the event sink to receive the event notification according to preferences of a user of the client device; and

rendering the received event notification, by the selected second application, instead of rendering the inbound message by the first application.

15. The method according to claim 14, wherein the second application is an audio player and the rendering comprises audibly playing the received event notification from the audio player using a text-to-speech generator.