PARTIAL MESSAGE STREAMING

• US 20070177583A1
• Filed: 08/31/2006
• Published: 08/02/2007
• Est. Priority Date: 01/31/2006
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Cabrera, Luis Felipe, Waingold, Elliot L., Wolf, Kenneth D., Osovetsky, Eugene, Christensen, Erik B., Vernal, Michael S., Coulson, Michael J.
• Application Number:
  US11/469,437
• Publication Number:
  US 20070177583A1
• Time in Patent Office: Days
• US Class Current: 370/352
• CPC Class Codes: G06F 2209/461 Bridge
• CPC Class Codes: G06F 2209/463 Naming
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449
• CPC Class Codes: G06Q 10/00 Administration; Management
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/06 Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/165 Combined use of TCP and UDP protocols; selection criteria therefor
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 69/328 in the presentation layer [OSI layer 6]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

Embodiments provided herein support large messages by formatting at least a portion of the message in the form of a transport stream. More specifically, embodiments provide a SOAP model that can stream an object for a message without loading the entire message into an intermediate buffer. Accordingly, one embodiment supports loading SOAP headers into memory, yet streaming the body. This would allow, for example, large attachments (e.g., a video file) to accompany the SOAP message in the body, while still supporting random access to message headers. Accordingly, embodiments provide a SOAP data model that allows a developer to create an object and specify whether or not portions of the message should be buffered or streamed.

Claims

1. In a distributed messaging system, a method of efficiently sending large messages by limiting the amount of the message that is loaded into an intermediate buffer before sending across a wire to a destination node, the method comprising:

accessing a message that is to be sent across the wire to a destination node;

loading a first portion of the message into an intermediate buffer for random access thereto;

formatting a second portion of the message, different from the first portion, in the form of a transport stream; and

streaming the second portion of the message across a wire to the destination node without loading the second portion in the intermediate buffer in order to reduce buffer requirements for sending large messages.

2. The method of claim 1, wherein the message is a SOAP message and the first portion includes one or more headers, and the second portion is an attachment within a body of the message.

3. The method of claim 1, wherein the streaming of the second portion is done using a transport connection that is dedicated to stream the message.

4. The method of claim 3, wherein the type of transport supports exchange patterns of one or more request/reply channel, output/input channel, or full duplex channel.

5. The method of claim 3, wherein upon sending the message the method further comprises:

closing the transport connection in order to notify the destination node that the transmission is complete.

6. The method of claim 3, wherein the transport connection is one of a TCP socket, named pipe, or HTTP connection.

7. The method of claim 6, wherein the client is configured to send the message across one of the transport connections using a transfer mode property of a channel factory.

8. The method of claim 6, wherein the client is configured to send the message across one of the transport connections using a transport binding element.

9. In a distributed messaging system, a computer program product for implementing a method of efficiently sending large messages by limiting the amount of the message that is loaded into an intermediate buffer before sending across a wire to a destination node, the computer program product comprising one or more computer readable media having stored thereon computer executable instructions that, when executed by a processor, can cause the distributed messaging system to perform the following:

access a message that is to be sent across the wire to a destination node;

load a first portion of the message into an intermediate buffer for random access thereto;

format a second portion of the message, different from the first portion, in the form of a transport stream; and

stream the second portion of the message across a wire to the destination node without loading the second portion in the intermediate buffer in order to reduce buffer requirements for sending large messages.

10. The computer program product of claim 9, wherein the message is a SOAP message and the first portion includes one or more headers, and the second portion is an attachment within a body of the message.

11. The computer program product of claim 9, wherein the streaming of the second portion is done using a transport connection that is dedicated to stream the message.

12. The computer program product of claim 11, wherein the type of transport supports exchange patterns of one or more request/reply channel, output/input channel, or full duplex channel.

13. The computer program product of claim 11, wherein upon sending the message the computer program product further comprises computer executable instructions that cause the distributed messaging system to perform the following:

close the transport connection in order to notify the destination node that the transmission is complete.

14. The computer program product of claim 11, wherein the transport connection is one of a TCP socket, named pipe, or HTTP connection.

15. The computer program product of claim 14, wherein the client is configured to send the message across one of the transport connections using a transfer mode property of a channel factory.

16. The computer program product of claim 14, wherein the client is configured to send the message across one of the transport connections using a transport binding element.

17-26. -26. (canceled)