Queued component interface passing for results outflow from queued method invocations

• US 20050125804A1
• Filed: 01/06/2005
• Published: 06/09/2005
• Est. Priority Date: 12/15/1999
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Chopra, Gagan, Helland, Patrick J., Dievendorff, Richard, Al-Ghosein, Mohsen
• Granted Patent: US 7,634,777 B2
• Time in Patent Office: Days
• US Class Current: 719/315
• CPC Class Codes: G06F 2209/548 Queue
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449

Abstract

Queued component interface passing provides a way for a queued component to convey results of processing a client program'"'"'s method invocations made asynchronously via a queue. A queued component recorder for a “processing” queued component operates to marshal-by-value a method invocation parameter that is reference to another queued component recorder for another “results” queued component into a data stream of recorded method invocations, which is then submitted as a message to a queue associated with the processing queued component. On receipt of the message from the queue, a queued component player for the processing queued component unmarshals the reference to the other queued component recorder and passes this reference to the processing queued component. The processing queued component uses the passed reference to invoke methods of the results queued component through its message queue, which conveys the processing queued component'"'"'s results.

Claims

1. (canceled)

2. (canceled)

3. (canceled)

4. (canceled)

5. (canceled)

6. (canceled)

7. (canceled)

8. (canceled)

9. (canceled)

10. (canceled)

11. (canceled)

12. (canceled)

13. (canceled)

14. (canceled)

15. (canceled)

16. (canceled)

17. A method of yielding results from processing work of a first queued component to a second queued component, where the work of the first queued component is initiated by method invocations delivered via a first message queue, and the second queued component is dispatched method invocations delivered into a second message queue, the method comprising:

responsive to a client program issuing a first set of method invocations for the first queued component, marshaling data for the method invocations of the first set into a message to be enqueued into the first message queue; and

when marshaling an interface pointer reference to the second queued component in any of the method invocations issued by the client program for the first queued component, incorporating interface passing information in the data marshaled into the message, the interface passing information designating to enqueue any method invocation by the first queued component on an interface of the second queued component referenced by the interface pointer reference into the second message queue.

18. The method of claim 17 further comprising, responsive to the first queued component issuing a second set of method invocations on the interface of the second queued component referenced by the interface pointer reference, enqueueing the method invocations of the second set into the second message queue.

19. The method of claim 17 further comprising:

passing the interface pointer reference in queued method invocations to multiple further queued components; and

responsive to the first queued component and the multiple queued components issuing sets of method invocations on the interface of the second queued component, enqueueing the method invocations of each such set into the second message queue.

20. At least one computer-readable storage medium having stored thereon a software program executable on a computer to perform a method of yielding results from processing work of a first queued component to a second queued component, where the work of the first queued component is initiated by method invocations delivered via a first message queue, and the second queued component is dispatched method invocations delivered into a second message queue, the method comprising:

responsive to a client program issuing a first set of method invocations for the first queued component, marshaling data for the method invocations of the first set into a message to be enqueued into the first message queue; and

when marshaling an interface pointer reference to the second queued component in any of the method invocations issued by the client program for the first queued component, incorporating interface passing information in the data marshaled into the message, the interface passing information designating to enqueue any method invocation by the first queued component on an interface of the second queued component referenced by the interface pointer reference into the second message queue.

21. The at least one computer-readable storage medium of claim 20 wherein the method further comprises, responsive to the first queued component issuing a second set of method invocations on the interface of the second queued component referenced by the interface pointer reference, enqueueing the method invocations of the second set into the second message queue.

22. The at least one computer-readable storage medium of claim 20 wherein the method further comprises:

passing the interface pointer reference in queued method invocations to multiple further queued components; and

responsive to the first queued component and the multiple queued components issuing sets of method invocations on the interface of the second queued component, enqueueing the method invocations of each such set into the second message queue.

23. A computer-based system of yielding results from processing work of a first queued component to a second queued component, where the work of the first queued component is initiated by method invocations delivered via a first message queue, and the second queued component is dispatched method invocations delivered into a second message queue, the system comprising:

means for marshaling data into a message to be enqueued into the first message queue responsive to a client program issuing a first set of method invocations for the first queued component, the marshaled data representing the method invocations of the first set; and

means for incorporating interface passing information in the data marshaled into the message when marshaling an interface pointer reference to the second queued component in any of the method invocations issued by the client program for the first queued component, the interface passing information designating to enqueue any method invocation by the first queued component on an interface of the second queued component referenced by the interface pointer reference into the second message queue.

24. The system of claim 23 further comprising means responsive to the first queued component issuing a second set of method invocations on the interface of the second queued component referenced by the interface pointer reference for enqueueing the method invocations of the second set into the second message queue.

25. The system of claim 23 further comprising:

means for passing the interface pointer reference in queued method invocations to multiple further queued components; and

means responsive to the first queued component and the multiple queued components issuing sets of method invocations on the interface of the second queued component for enqueueing the method invocations of each such set into the second message queue.