Retrieving events from a queue

• US 7,624,396 B1
• Filed: 02/26/2004
• Issued: 11/24/2009
• Est. Priority Date: 02/26/2004
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Isenberg, Miguel
• Primary Examiner(s): Zhen; Li B
• Assistant Examiner(s): Cao; Diem K
• Application Number:
  US10/789,523
• Time in Patent Office: 2,098 Days
• Field of Search: 712 28- 43, 712200-207, 712216-248, 718100-103, 718106-108, 719310-320, 719328-332
• US Class Current: 719/314
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

Methods and apparatus, including computer program products, implementing and using techniques for retrieving events from an event port. A request to retrieve a specified number of events from an event port to which completed events are posted by one or more event sources is received from a computer software application. It is determined whether the specified number of events is available at the event port. If the specified number of events is available at the event port, the specified number of events is retrieved from the event port and the retrieved events are returned to the requesting computer software application. If fewer events than the specified number of events are available at the event port, the request is placed in a request queue with requests to be processed at a later time and the request queue is ordered based on priorities of the requests in the request queue.

Claims

1. In a computer system, a method for retrieving events from an event port, the method comprising:

receiving from a computer software application, a request to retrieve a specified number of events from an event port to which completed events are posted by one or more event sources;

determining whether the specified number of events is available at the event port;

if the specified number of events is available at the event port, retrieving the specified number of events from the event port and returning the retrieved events to the requesting computer software application;

if fewer events than the specified number of events are available at the event port, placing the request in a request queue with requests to be processed at a later time and ordering the request queue based on priorities of the requests in the request queue, wherein the specified number of events to be retrieved from the event port is used to determine a relative priority of the request in the request queue with respect to other requests in the request queue; and

changing the priorities of the requests in the request queue based on the number of events available at the event port, wherein the changing is further based on a specified number of events to be retrieved as part of at least one request received in response to at least one indication about the number of events available at the event port.

2. The method of claim 1, wherein ordering comprises:

placing requests with a higher priority ahead of requests with lower priority in the request queue.

3. The method of claim 1, wherein ordering comprises:

placing two or more requests with a same priority in a stack; and

placing the stack in the request queue based on the priority of the requests in the stack.

4. The method of claim 1, wherein a priority of a request is inversely proportional to the specified number of events.

5. The method of claim 1, wherein the request queue comprises requests generated by one or more computer software application threads.

6. The method of claim 1, wherein the request queue comprises requests generated by one or more computer software application processes.

7. The method of claim 1, wherein the number of events to be retrieved from the event port is specified by the computer software application.

8. The method of claim 7, wherein the number of events to be retrieved from the event port is specified by the computer software application based on user input.

9. The method of claim 1, further comprising:

if fewer events than the specified number of events are available at the event port, determining whether there are any requests in the request queue that can be satisfied by the available number of events at the event port; and

if there are requests in the request queue that can be satisfied, retrieving the specified number of events from the event port for one or more such requests and returning the retrieved events to the requesting computer software application.

10. The method of claim 1, wherein the request has an associated timeout prior to which the request must be satisfied.

11. The method of claim 10, further comprising:

if a timeout occurs for a request while the request is in the request queue, retrieving all the available events at the event port at the time of timeout; and

returning the request to the computer software application with the retrieved events.

12. The method of claim 1, further comprising:

returning an empty request to the requesting software application if the request cannot be satisfied.

13. The method of claim 12, wherein returning comprises:

returning the empty request together with an error code indicating the cause for why the request cannot be satisfied.

14. The method of claim 1, further comprising:

returning an empty request to the requesting software application if one or more of the following error conditions occur;

the request comprises an invalid event port identifier, an event or a list of events list cannot be delivered, a timeout argument is out of range, and a timeout interval expires before an expected number of events has been posted to the event port.

15. The method of claim 1, wherein returning the retrieved events to the requesting computer software application comprises returning one or more of:

one or more detected events, one or more event source identifiers where the detected events were generated, one or more objects specific to an event source, and one or more user defined values.

16. The method of claim 1, further comprising:

if the specified number of events is zero, identifying the number of available events at the event port; and

informing the requesting computer software application of how many events are available at the event port.

17. The method of claim 1, wherein the events are asynchronous events.

18. The method of claim 1, wherein the events are transaction events.

19. The method of claim 1, wherein the event sources include one or more of:

input devices, output devices, timers, signals, file updates, applications, system libraries, and drivers.

20. A computer program product, stored on a machine-readable medium, comprising instructions operable to cause a computer to:

receive from a computer software application, a request to retrieve a specified number of events from an event port to which completed events are posted by one or more event sources;

determine whether the specified number of events is available at the event port;

if the specified number of events is available at the event port, retrieve the specified number of events from the event port and returning the retrieved events to the requesting computer software application;

if fewer events than the specified number of events are available at the event port, place the request in a request queue with requests to be processed at a later time and order the request queue based on priorities of the requests in the request queue, wherein the specified number of events to be retrieved from the event port is used to determine a relative priority of the request in the request queue with respect to other requests in the request queue; and

changing the priorities of the requests in the request queue based on the number of events available at the event port, wherein the changing is further based on a specified number of events to be retrieved as part of at least one request received in response to informing the computer application software about the number of events available at the event port.

21. The computer program product of claim 20, wherein the instructions to order comprise instructions to:

place requests with a higher priority ahead of requests with lower priority in the request queue.

22. The computer program product of claim 20, wherein the instructions to order comprise instructions to:

place two or more requests with a same priority in a stack; and

place the stack in the request queue based on the priority of the requests in the stack.

23. The computer program product of claim 20, wherein a priority of a request is inversely proportional to the specified number of events.

24. The computer program product of claim 20, wherein the request queue comprises requests generated by one or more computer software application threads.

25. The computer program product of claim 20, wherein the request queue comprises requests generated by one or more computer software application processes.

26. The computer program product of claim 20, wherein the number of events to be retrieved from the event port is specified by the computer software application.

27. The computer program product of claim 26, wherein the number of events to be retrieved from the event port is specified by the computer software application based on user input.

28. The computer program product of claim 20, further comprising instructions to:

determine whether there are any requests in the request queue that can be satisfied by the available number of events at the event port, if fewer events than the specified number of events are available at the event port; and

retrieve the specified number of events from the event port for one or more such requests and returning the retrieved events to the requesting computer software application, if there are requests in the request queue that can be satisfied.

29. The computer program product of claim 20, wherein the request has an associated timeout prior to which the request must be satisfied.

30. The computer program product of claim 29, further comprising instructions to:

retrieve all the available events at the event port at the time of timeout if a timeout occurs for a request while the request is in the request queue; and

return the request to the computer software application with the retrieved events.

31. The computer program product of claim 20, further comprising instructions to:

return an empty request to the requesting software application if the request cannot be satisfied.

32. The computer program product of claim 31, wherein the instructions to return comprise instructions to:

return the empty request together with an error code indicating the cause for why the request cannot be satisfied.

33. The computer program product of claim 20, further comprising instructions to:

return an empty request to the requesting software application if one or more of the following error conditions occur;

the request contains an invalid event port identifier, an event or a list of events list cannot be delivered, a timeout argument is out of range, and a timeout interval expires before an expected number of events has been posted to the event port.

34. The computer program product of claim 20, wherein the instructions to return the retrieved events to the requesting computer software application comprise instructions to return one or more of:

one or more detected events, one or more event source identifiers where the detected events were generated, one or more objects specific to an event source, and one or more user defined values.

35. The computer program product of claim 20, further comprising instructions to:

identify the number of available events at the event port if the specified number of events is zero; and

inform the requesting computer software application of how many events are available at the event port.

36. The computer program product of claim 20, wherein the events are asynchronous events.

37. The computer program product of claim 20, wherein the events are transaction events.

38. The computer program product of claim 20, wherein the event sources include one or more of:

input devices, output devices, timers, signals, file updates, applications, system libraries, and drivers.

39. A computer system for retrieving transaction events generated by one or more event sources in a computer system, comprising:

a processor;

an event queue configured to receive transaction events generated by one or more event sources, the event queue being accessible through an event port;

a request queue configured to hold requests to retrieve transaction events from the event queue, each request having an associated priority determining a place of the request in the request queue, wherein the specified number of events to be retrieved from the event port is used to determine a relative priority of the request in the request queue with respect to other requests in the request queue; and

a queue manager when executed by the processor, operable to;

receive requests from a computer software application;

organize the received requests in the request queue;

determine whether a sufficient number of events are available in the event queue to fill a request with a highest priority in the request queue;

if a sufficient number of events is available in the event queue, retrieve the events needed to fill the request with the highest priority in the request queue through the event port and return the filled request to the requesting computer software application; and

change the associated priorities of the requests in the request queue based on the number of events available in the event queue, wherein the changing is further based on a specified number of events to be retrieved as part of at least one request received in response to a value set to the number of events available in the event queue.

40. The computer system of claim 39, wherein the request queue includes one or more stacks, each stack containing two or more requests with a same priority, the stacks being ordered in the request queue based on the priority of the requests in the respective stacks.

41. The computer system of claim 39, wherein a request in the request queue has an associated timeout prior to which the request must be satisfied.