Method and apparatus for providing and integrating high-performance message queues in a user interface environment

• US 6,954,933 B2
• Filed: 06/26/2001
• Issued: 10/11/2005
• Est. Priority Date: 10/30/2000
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Stall, Jeffrey E.
• Primary Examiner(s): Courtenay, III, St. John
• Assistant Examiner(s): ANYA, CHARLES E
• Application Number:
  US09/892,951
• Publication Number:
  US 20020052978A1
• Time in Patent Office: 1,568 Days
• Field of Search: 719 31-318, 715700-866, 718100-108, 709213-216, 711147-148, 345700-866
• US Class Current: 719/314
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces

Abstract

A method and apparatus is provided for providing and integrating high-performance message queues. “Contexts” are provided that allow independent worlds to be created and execute in parallel. A context is created with one or more threads. Each object is created with context affinity, allowing any thread inside the context to modify the object or process pending messages. Threads in a different context are unable to modify the object or process pending messages for that context. To help achieve scalability and context affinity, both global and thread-local data is often moved into the context. Remaining global data has independent locks, providing synchronized access for multiple contexts. Each context has multiple message queues to create a priority queue. There are default queues for sent messages and posted messages, carry-overs from legacy window managers, with the ability to add new queues on demand. A queue bridge is also provided for actually processing the messages.

Claims

1. A computer implemented method for sending a message via a high-performance message queue, comprising:

providing a message queue associated with a context;

executing a user interface thread associated with said context;

receiving a request from said user interface thread to send a message to a second user interface thread;

determining whether said second user interface thread is associated with said context; and

in response to determining that said second user interface thread is associated with said context, sending said message from said user interface thread directly to said second user interface thread, thereby bypassing said message queue.

2. The method of claim 1, further comprising:

in response to determining that said second user interface thread is not associated with said context, atomically adding said message to a queue associated with a second context.

3. The method of claim 2, further comprising:

atomically providing an indication to said second context that a message has been added to said queue associated with said second context.

4. The method of claim 3, further comprising:

waiting for an indication that said message added to said queue associated with said second context has been processed; and

processing additional messages while waiting for said indication.

5. The method of claim 4, wherein atomically adding said message to a queue associated with a second context comprises locking said message and atomically adding said message to a singly-linked list associated with said context.

6. A computer apparatus for sending a message via a high-performance message queue, comprising:

(a) a memory; and

(b) a processor connected to the memory, wherein the processor is configured to operate in accordance with executable instructions that, when executed, cause the processor to;

i. provide a message queue associated with a context;

ii. execute a user interface thread associated with said context;

iii. receive a request from said user interface thread to send a message to a second user interface thread;

iv. determine whether said second user interface thread is associated with said context; and

v. in response to determining that said second user interface thread is associated with said context, send said message from said user interface thread directly to said second user interface thread, thereby bypassing said message queue.

7. The computer apparatus of claim 6, wherein the processor is configured to operate in accordance with executable instructions that, when executed, further cause the processor to:

in response to determining that said second user interface thread is not associated with said context, atomically add said message to a queue associated with a second context.

8. The computer apparatus of claim 7, wherein the processor is configured to operate in accordance with executable instructions that, when executed, further cause the processor to:

atomically provide an indication to said second context that a message has been added to said queue associated with said second context.

9. The computer apparatus of claim 8, wherein the processor is configured to operate in accordance with executable instructions that, when executed, further cause the processor to:

wait for an indication that said message added to said queue associated with said second context has been processed; and

process additional messages while waiting for said indication.

10. The computer apparatus of claim 9, wherein to atomically add said message to a queue associated with a second context further comprises locking said message and atomically adding said message to a singly-linked list associated with said context.

11. A computer-readable medium for performing a method for sending a message via a high-performance message queue, the method comprising:

providing a message queue associated with a context;

executing a user interface thread associated with said context;

receiving a request from said user interface thread to send a message to a second user interface thread;

determining whether said second user interface thread is associated with said context; and

in response to determining that said second user interface thread is associated with said context, sending said message from said user interface thread directly to said second user interface thread, thereby bypassing said message queue.

12. The computer-readable medium of claim 11, further comprising:

in response to determining that said second user interface thread is not associated with said context, atomically adding said message to a queue associated with a second context.

13. The computer-readable medium of claim 12, further comprising:

atomically providing an indication to said second context that a message has been added to said queue associated with said second context.

14. The computer-readable medium of claim 13, further comprising:

waiting for an indication that said message added to said queue associated with said second context has been processed; and

processing additional messages while waiting for said indication.

15. The computer-readable medium of claim 14, wherein atomically adding said message to a queue associated with a second context comprises locking said message and atomically adding said message to a singly-linked list associated with said context.