Queued component interface passing for results outflow from queued method invocations

• US 7,634,777 B2
• Filed: 01/06/2005
• Issued: 12/15/2009
• Est. Priority Date: 12/15/1999
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Chopra, Gagan, Helland, Patrick J., Dievendorff, Richard, Al-Ghosein, Mohsen M.
• Primary Examiner(s): Zhen; Li B
• Application Number:
  US11/034,517
• Publication Number:
  US 20050125804A1
• Time in Patent Office: 1,804 Days
• Field of Search: 719/313, 719/315, 719/316
• 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. 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 client-side queued component to a server-side queued component, where the work of the client-side queued component is initiated by method invocations delivered via a client-side message queue, and the server-side queued component is dispatched method invocations delivered into a server-side message queue, the method comprising:

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

when marshaling an interface pointer reference to the server-side queued component in any of the method invocations issued by the client program for the client-side 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 client-side queued component on an interface of the server-side queued component referenced by the interface pointer reference into the server-side message queue;

automatically detecting a passed interface pointer reference; and

in response to automatically detecting the passed interface pointer reference, setting up a persistent object facility to automatically queue any method invocations issued by the client-side queued component with the passed interface pointer reference into the server-side message queue associated with the server-side queued component.

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

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

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

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

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

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

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

means for automatically detecting a passed interface pointer reference; and

means for setting up, in response to automatically detecting the passed interface pointer reference, a persistent object facility to automatically queue any method invocations issued by the client-side queued component with the passed interface pointer reference into the server-side message queue associated with the server-side queued component.

5. The system of claim 4 further comprising means responsive to the client-side queued component issuing a second set of method invocations on the interface of the server-side queued component referenced by the interface pointer reference for enqueueing the method invocations of the second set into the server-side message queue.

6. A method of yielding results from processing work of a client-side queued component to a server-side queued component, where the work of the client-side queued component is initiated by method invocations delivered via a client-side message queue, and the server-side queued component is dispatched method invocations delivered into a server-side message queue associated with the server-side queued component, the method comprising:

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

when marshaling an interface pointer reference to the server-side queued component in any of the method invocations issued by the client program for the client-side 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 client-side queued component on an interface of the server-side queued component referenced by the interface pointer reference into the server-side message queue;

automatically detecting a passed interface pointer reference;

in response to automatically detecting the passed interface pointer reference, setting up a persistent object facility to automatically queue any method invocations issued by the client-side queued component with the passed interface pointer reference into the server-side message queue associated with the server-side queued component.

7. The method of claim 6, further comprising automatically detecting an interface pointer embedded within a data structure that is passed as a direct parameter.

8. The method of claim 6, further comprising automatically detecting an interface pointer embedded within a data structure that is passed as a direct parameter.

9. The method of claim 6, wherein incorporating interface passing information in the data marshaled into the message further comprises incorporating a process name associated with the client-side queued component.

10. The method of claim 6, wherein incorporating interface passing information in the data marshaled into the message further comprises incorporating an indicator of a transaction associated with the client-side queued component and an indication of a computer associated with the client-side queued component.

11. The method of claim 6, wherein incorporating interface passing information in the data marshaled into the message further comprises incorporating an indicator of a transaction associated with the client-side queued component and an indication of a computer associated with the client-side queued component.

12. The method of claim 6, wherein the server-side message queue is associated exclusively with the client-side message queue.

13. A system for yielding results from processing work of a client-side queued component to a server-side queued component, where the work of the client-side queued component is initiated by method invocations delivered via a client-side message queue, and where the server-side queued component is dispatched method invocations delivered into a server-side message queue associated with the server-side queued component, the system comprising:

one or more computers comprising one or more processors, wherein the one or more computers are programmed to perform a method, the method comprising,

responsive to a client program issuing a first set of method invocations for the client-side queued component, the one or more processors marshaling data for the method invocations of the first set into a message to be enqueued into the client-side message queue,

when marshaling an interface pointer reference to the server-side queued component in any of the method invocations issued by the client program for the client-side queued component, the one or more processors incorporating interface passing information in the data marshaled into the message, the interface passing information designating to enqueue, into the server-side message queue, any method invocation by the client-side queued component on an interface of the server-side queued component that is referenced by the interface pointer reference,

the one or more processors automatically detecting a passed interface pointer reference, and

in response to automatically detecting the passed interface pointer reference, the one or more processors setting up a persistent object facility to automatically queue any method invocations issued by the client-side queued component with the passed interface pointer reference into the server-side message queue associated with the server-side queued component.