Event filtering at a performance-based interface

• US 20050193391A1
• Filed: 03/01/2004
• Published: 09/01/2005
• 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.
• Granted Patent: US 7,681,204 B2
• Time in Patent Office: Days
• US Class Current: 719/313
• 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, comprising:

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

a filter component in communication with the destination that dynamically allows only one or more relevant responses from the destination to transition the interface to the source.

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 part of at least one of native code and managed code.

4. The system of claim 1, the destination issues a callback to the source, in response the filter component permits only a relevant response to the callback to transmitted to the destination.

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

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

7. 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.

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

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

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

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

12. 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.

13. The system of claim 1, the source notifies a native layer that an event handler has attached or detached.

14. The system of claim 1, 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.

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

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

17. 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.

18. 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.

19. A system that facilitates a performance enhancement in message-based computing, comprising:

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 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 allows only one or more relevant responses of the native code framework to transition the interface to the managed code framework.

20. The system of claim 19, the filter component is part of the native code framework.

21. The system of claim 19, the filter component only allows the one or more responses across the interface that are relevant to the request.

22. The system of claim 19, further comprising a managed code filter component that is part of the managed code framework.

23. The system of claim 19, further comprising 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.

24. The system of claim 19, the filter component only processes events that are registered.

25. The system of claim 19, 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.

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

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

29. The system of claim 19, 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.

30. A computer-readable medium having computer-executable instructions for performing a method of managing messages across a performance-based interface, the method comprising:

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

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

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

transmitting the relevant responses across the interface to the source.

31. The method of claim 30, the act of filtering occurs on the destination side of the interface.

32. The method of claim 30, 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 interface to the destination.

34. The method of claim 30, further comprising tracking the attached event with the native code.

36. The method of claim 30, the act of detecting occurs in response to the act of initializing, when the custom object has been detected.

37. The method of claim 30, the act of forwarding occurs only for the one or more messages associated with the modified message handling.

38. The method of claim 30, further comprising processing a callback from the native code framework such that only responses relevant to the callback are transmitted across the interface from the managed code framework.

33. A method of managing messages across a performance-based interface, comprising:

receiving the performance-based 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 a one or more responses of the native code associated with the event;

filtering the one or more responses of the native code to determine the relevant responses associated with event; and

transmitting the relevant responses across the interface to the managed code only when the associated event handler is registered.

35. A method of managing messages across a performance-based interface, comprising:

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

initializing one or more objects to determine the existence of a custom object;

detecting if message handling of the custom object has been modified;

notifying the native code framework that one or more messages associated with the modified message handling are of interest; and

forwarding responses to one or more messages to the managed code framework during a lifetime of the custom object.

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

means for receiving the performance-based 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 a one or more responses of the native code associated with the event;

means for filtering the one or more responses of the native code to determine the relevant responses associated with event; and

means for transmitting the relevant responses across the interface to the managed code only when the associated event handler is registered.

40. The system of claim 39, further comprising means for unregistering the one or more event handlers when the associated events have expired.