DYNAMIC LISTENER LOOKUP AND IMPLEMENTATION

• US 20110219384A1
• Filed: 03/05/2010
• Published: 09/08/2011
• Est. Priority Date: 03/05/2010
• Status: Abandoned Application

• Current Assignee: Hit Concepts LLC
• Original Assignee: Hit Concepts LLC
• Inventors: Black, Cara Lee, Clark, Michael Charles, Rose, Jason Edward
• Application Number:
  US12/718,741
• Publication Number:
  US 20110219384A1
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 3/00 Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

Embodiments are directed to dynamically determining event listeners. A computer system sends a query to a data store to determine which event listeners are configured to listen for an indicated event. The event listeners are registered in the data store without the software module having to explicitly declare its event listeners. The computer system receives from the data store an indication of those event listeners that are configured to listen for the event. The computer system also sends the event to those event listeners indicated by the data store as being registered to receive notification of the event'"'"'s occurrence.

Claims

1. At a computer system including a processor and a memory, in a computer programming environment configured to implement an observer pattern, a computer-implemented method for dynamically determining event listeners, the method comprising:

an act of sending a query to a data store to determine which event listeners are configured to listen for an indicated event, wherein the event listeners are registered in the data store without the software module having to explicitly declare its event listeners;

an act of receiving from the data store an indication of those event listeners that are configured to listen for the event; and

an act of sending the event to those event listeners indicated by the data store as being registered to receive notification of the event'"'"'s occurrence.

2. The method of claim 1, wherein at least one of the registered event listeners is rewritten in a generic manner such that the event listener can be applied to any software object.

3. The method of claim 2, further comprising an act of a second, different software module implementing the rewritten generic event listener as part of the second software module'"'"'s execution.

4. The method of claim 3, further comprising an act of updating a software application'"'"'s view based on any changes made to the second software module'"'"'s execution.

5. The method of claim 3, wherein the rewritten generic event listener allows software modules to implement other software components without providing module-specific code support.

6. The method of claim 1, wherein a plurality of listeners for different software modules are registered in a master configuration file stored in the data store.

7. The method of claim 6, wherein the master configuration file includes a value for each listener which allows data to be passed between the plurality of listeners, the value identifying to the corresponding software modules what data is being passed.

8. The method of claim 1, further comprising an act of implementing an access control mechanism to limit when one or more of the listeners are triggered.

9. The method of claim 1, further comprising recursively performing each act of claim 1 each time the software module is initiated.

10. The method of claim 1, further comprising:

an act of parsing a view comprising at least the output generated by the software module;

an act of loading the parsed view; and

an act of injecting one or more software components into the loaded view.

11. The method of claim 10, wherein the injecting includes a plurality of forms including the following:

prepending, appending, before, after and wrapping.

12. The method of claim 1, wherein the event comprises a user interaction with a graphical user interface corresponding to the software module.

13. The method of claim 1, wherein the event listeners are accessible through a plurality of different interfaces.

14. At a computer system including a processor and a memory, in a computer programming environment configured to implement an observer pattern, a computer-implemented method for providing dynamically determined event listeners to a software module, the method comprising:

an act of inserting into a database information identifying one or more event listeners that are configured to listen for events related to an identified software module;

an act of receiving an event trigger at a software application indicating that an event related to the identified software module has occurred;

an act of the application querying the database to determine which listeners are configured to listen for events related to the identified software module;

an act of receiving from the database an indication of those listeners which are configured to listen for events related to the identified software module; and

an act of sending the triggered event to those event listeners indicated as being related to the identified software module.

15. The method of claim 14, wherein the information identifying one or more event listeners that are configured to listen for events related to an identified software module is inserted into the database by a software module developer.

16. The method of claim 15, wherein the software module developer registers a portion of metadata identifying internal structure characteristics of the software module such that changes to the software module'"'"'s internal structure are made according to the added metadata.

17. The method of claim 14, wherein the information identifying one or more event listeners that are configured to listen for events related to an identified software module is stored in an XML configuration file.

18. The method of claim 14, further comprising an act of the identified software module transparently modifying a second different module without notifying the second module of the modifications.

19. A computer program product for implementing a method for providing modular software functionality using generic callbacks managed in a data store, the computer program product comprising one or more computer-readable storage media having stored thereon computer-executable instructions that, when executed by one or more processors of the computing system, cause the computing system to perform the method, the method comprising:

an act of sending a query to a data store to determine which event listeners are configured to listen for an indicated event, wherein the event listeners are registered in the data store without the software module having to explicitly declare its event listeners;

an act of an act of receiving from the data store an indication of those event listeners that are configured to listen for the event; and

an act of sending the event to those event listeners indicated by the data store as being registered to receive notification of the event'"'"'s occurrence.

20. The computer program product of claim 19, further comprising:

an act of parsing a view comprising at least the output generated by the software module;

an act of loading the parsed view; and

an act of injecting one or more software components into the loaded view.