Event filtering at a performance-based interface

• US 7,681,204 B2
• Filed: 03/01/2004
• Issued: 03/16/2010
• Est. Priority Date: 03/01/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Lorton, Christopher W., Demsey, Seth M., Schaeffer, Katrina, Wrighton, David C., Boilen, Michael G., de Guerre, Jamie A.
• Primary Examiner(s): Nguyen; Van H
• Application Number:
  US10/790,522
• Publication Number:
  US 20050193391A1
• Time in Patent Office: 2,206 Days
• Field of Search: 719/318, 719/310, 719/328, 719/313
• US Class Current: 719/318
• CPC Class Codes: G06F 2209/543 Local
• CPC Class Codes: G06F 2209/545 Gui
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70

Abstract

Architecture that facilitates performance enhancement in message-based computing across a performance-based interface. When a request from a source is transmitted across the interface to a destination, a filter component in communication with the destination dynamically allows only one or more relevant responses from the destination to transition the interface to the source. This mechanism achieves an even tighter filtering of events while at the same time giving developers more flexibility over the events they choose to register, thereby enhancing the performance of message-based computing architectures by reducing unnecessary computation.

Claims

1. A system that facilitates a performance enhancement in message-based computing, the system comprising at least one processor and one or more computing devices configured with:

a performance-based event transmission interface across which a request from a source is transmitted to a destination; and

a filter component in communication with the destination that dynamically determines which response information is relevant in order to filter out any excess response information that is deemed irrelevant, such that allows only relevant responses from the destination are transmitted to the source via the performance-based event transmission interface, wherein the filter component is part of at least one of native code and managed code and wherein irrelevant responses are discarded;

wherein the source notifies a native layer that an event handler has attached or detached,

wherein the destination issues a callback to the source, in response the filter component permits only a relevant response to the callback to be transmitted to the destination, and

wherein the filter component is notified by the source when an event handler has attached to or detached from a source object, and forwards the one or more responses only when the associated event handlers are attached.

2. The system of claim 1, the source comprises at least one of native code and managed code, and the destination comprises at least one of native code and managed code.

3. The system of claim 1, the filter component is integrated into an operating system.

4. The system of claim 1 is employed in a small footprint execution environment that has reduced resources.

5. The system of claim 1, the source is part of a managed code framework that includes a graphical user interface (GUI) application that transmits an event for processing by the destination, which destination is part of native code.

6. The system of claim 1, further comprising a classifier that makes an inference about processes that can be automatically performed.

7. A computer readable storage medium having stored thereon computer executable instructions for carrying out the system of claim 1.

8. A computer that employs the system of claim 1.

9. A server that employs the system of claim 1.

10. The system of claim 1, the source is associated with a GUI such that the request receives only the one or more responses from a graphics/windowing/events system that are relevant to the request.

11. The system of claim 1, the source can dynamically inspect at least one of properties, methods, and events implemented on a source object.

12. The system of claim 1, the source utilizes reflection during initialization of an object to determine the presence of a custom object.

13. The system of claim 1, the source utilizes reflection during initialization of an object to determine if message handling has been modified in a custom object.

14. The system of claim 1, the source utilizes type introspection to determine the presence of a custom object, in response to which the destination is notified that a message associated with the custom object is of interest and will be forwarded from the destination for a lifetime of the custom object.

15. A system that facilitates a performance enhancement in message-based computing, the system comprising at least one processor and one or more computing devices configured with:

a managed code framework that generates a request;

a native code framework that receives the request and issues one or more responses thereto;

a performance-based event transmission interface between the managed code framework and the native code framework across which the request is passed and the one or more responses are transmitted; and

a filter component in communication with the native code framework that dynamically determines which response information is relevant in order to filter out any excess response information that is deemed irrelevant, such that allows only relevant responses of the native code framework are transmitted to the managed code framework via the performance-based event transmission interface, wherein irrelevant responses are discarded; and

a managed code filter component that is part of the managed code framework, which managed code filter processes a callback from the native code framework and only forwards responses from the managed code to the native code that are relevant to the callback,

wherein the filter component is notified by the managed code framework when an event handler has at least one of registered and unregistered from a managed object and forwards the one or more responses only when the associated event handlers are registered.

16. The system of claim 15, the filter component is part of the native code framework.

17. The system of claim 15, the filter component only allows the one or more responses across the performance-based event transmission interface that are relevant to the request.

18. The system of claim 15, the filter component only processes events that are registered.

19. The system of claim 15, the managed code framework source utilizes type introspection during initialization of an object to determine the presence of a custom object.

20. The system of claim 15, the managed code framework utilizes type introspection during initialization of an object to determine if message handling has been modified in a custom object.

21. The system of claim 15, the managed code framework utilizes type introspection to determine the presence of a custom object, in response to which the native code framework is notified that a message associated with the custom object is of interest and will be forwarded from the native code framework for a lifetime of the custom object.

22. A computer-readable storage medium tangibly embodying thereon computer-executable instructions for performing a method of managing messages across a performance-based event transmission interface, the method comprising:

receiving the performance-based event transmission interface across which a request from a source is transmitted to a destination;

returning one or more responses to the request from the destination;

dynamically determining which response information is relevant in order to filter out any excess response information that is deemed irrelevant;

filtering the one or more responses to allow only responses that are relevant to the request to be transmitted from the destination to the source via the event transmission performance-based interface, wherein irrelevant responses are discarded; and

transmitting the relevant responses across the performance-based event transmission interface to the source;

wherein the source notifies a native layer that an event handler has attached or detached,

wherein the destination issues a callback to the source, in response the filter component permits only a relevant response to the callback to be transmitted to the destination,

wherein the filter component is notified by the source when an event handler has attached to or detached from a source object, and forwards the one or more responses only when the associated event handlers are attached.

23. The computer-readable storage medium of claim 22, the act of filtering occurs on the destination side of the performance-based event transmission interface.

24. The computer-readable storage medium of claim 22, the method further comprising at least one of the acts of:

transmitting the relevant responses according to priority criteria;

transmitting a request from the destination to the source;

filtering the one or more responses to allow only responses from the source that are relevant to the request; and

transmitting the relevant responses across the performance-based event transmission interface to the destination.

25. A method of managing messages across a performance-based event transmission interface, comprising

using one or more processors to perform the following computer-executable acts:

receiving the performance-based event transmission interface between a managed code and a native code;

registering an event handler for an event of a managed object;

notifying the native code that the event handler is registered;

returning one or more responses of the native code associated with the event;

dynamically determining which response information is relevant in order to filter out any excess response information that is deemed irrelevant;

filtering the one or more responses of the native code to determine the relevant responses associated with the event, such that only responses that are relevant to the request are allowed to be transmitted from the destination to the source via the performance-based event transmission interface, wherein irrelevant responses are discarded;

transmitting the relevant responses across the performance-based event transmission interface to the managed code only when the associated event handler is registered;

processing a request, issued by an application, associated with the event in accordance with a destination process;

unregistering the event;

notifying an event filter that the event is unregistered; and

signaling the application that the event has been unregistered.

26. The method of claim 25, further comprising tracking the attached event with the native code.

27. A system that facilitates the management of messages across a performance-based event transmission interface, comprising:

a processor;

system memory;

means for receiving the performance-based event transmission interface between a managed code and a native code;

means for registering an event handler for an event of a managed object;

means for notifying the native code that the event handler is registered;

means for returning one or more responses of the native code associated with the event;

means for dynamically determining which response information is relevant in order to filter out any excess response information that is deemed irrelevant;

means for filtering the one or more responses of the native code to determine the relevant responses associated with the event, such that only responses that are relevant to the request are allowed to be transmitted from the destination to the source via the event transmission performance-based interface, wherein irrelevant responses are discarded;

means for transmitting the relevant responses across the performance-based event transmission interface to the managed code only when the associated event handler is registered; and

means for unregistering the one or more event handlers when the associated events have expired.