EVENT FILTERING AT A PERFORMANCE-BASED INTERFACE

• US 20100146520A1
• Filed: 02/03/2010
• Published: 06/10/2010
• Est. Priority Date: 03/01/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Demsey, Seth M., Schaeffer, Katrina, Boilen, Michael G., de Guerre, Jamie A., Lorton, Christopher W., Wrighton, David C.
• Granted Patent: US 8,296,779 B2
• Time in Patent Office: Days
• US Class Current: 719/315
• 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 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.

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

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

4. The method of claim 1, 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.