Annotating portions of a message with state properties

• US 8,739,183 B2
• Filed: 04/15/2013
• Issued: 05/27/2014
• Est. Priority Date: 01/31/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Purdy, Douglas M., Christensen, Erik B., Wolf, Kenneth D., Waingold, Elliot L.
• Primary Examiner(s): Ho, Andy
• Assistant Examiner(s): Mudrick, Timothy A
• Application Number:
  US13/862,846
• Publication Number:
  US 20130232226A1
• Time in Patent Office: 407 Days
• Field of Search: 719/315
• US Class Current: 719/315
• 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 described herein provide for allowing processing code of a message to attach state thereto. More specifically, as a SOAP message is processed, various states known as properties (e.g., message security, message identifier, etc.) can be attached to the message for various purposes. In other words, embodiments provide for a properties object that represents a set of processing-level annotations to a message. These properties (representing the processing state of the headers or other portions of the message) can then be used by other component or modules for further processing purposes. Typically, these properties can then be removed (or sustained if desired) prior to transporting the SOAP message on the wire.

Claims

1. A system for performing a method of efficiently processing a SOAP message by attaching properties to a message object representing processing state of headers for the message in order to allow other operations to utilize such information, the system comprising one or more computer processors and computer memory having encoded thereon computer executable instructions which, when executed upon the one or more processors performs the method comprising:

receiving a SOAP message that includes a plurality of headers with content used to process the SOAP message;

processing at least a portion of content of a first header from the plurality of headers; and

based on the processing, annotating a message object with a property representing the processing state for the content of the first header such that other operations can use the property for further processing of the SOAP message, wherein the property representing the processing state for the content of the first header is contained within a properties object that represents a set of processing-level annotations to the message, the properties object added to the SOAP message outside the first header and the properties object comprising a set of name to object mappings, each name to object mapping representing a property representing a processing state for a particular content part of the SOAP message.

2. The system of claim 1, wherein the property is marked with a mark, the mark indicating one of the property should persist upon serialization of the SOAP message and the property should not persist upon serialization of the SOAP message.

3. The system of claim 1, wherein the property is not marked to indicate whether or not the property or should not persist upon serialization of the SOAP message, and wherein a default of not allowing the property to persist is invoked.

4. A system for performing a method of efficiently processing a SOAP message by attaching properties to a message object representing processing state for the SOAP message in order to allow other operations to utilize such information, the system comprising one or more computer processors and computer memory having encoded thereon computer executable instructions which, when executed upon the one or more processors performs the method comprising:

receiving a SOAP message that includes at least a header portion and a body portion;

processing at least a portion of the SOAP message, including one or both of the header portion or the body portion; and

based on the processing, annotating a message object within the body portion with a property representing the processing state of the header portion such that other operations can use the property for further processing of the SOAP message, wherein the property representing the processing state of the header portion is stored within a properties object that represents a set of processing-level annotations to the message, the properties object stored in a part of the message different than the header portion, the properties object comprising a set of name to object mappings, each name to object mapping representing a property representing a processing state for a particular content part of the SOAP message.

5. The system of claim 4, wherein the SOAP message includes at least one header with content, and wherein the property represents processing state of the content for the at least one header.

6. The system of claim 4, wherein the SOAP message includes at least one body portion with content, and wherein the property represents processing state of the content for the at least one body portion.

7. The system of claim 4, wherein the property represents processing state related to environmental information about how a message was received off a communication connection.

8. The system of claim 4, wherein the property is marked to indicate that either it should or should not persist upon serialization of the SOAP message.

9. The system of claim 4, wherein the property is not marked to indicate whether or not it should or should not persist upon serialization of the SOAP message, and wherein a default of not allowing the property to persist is invoked.

10. The system of claim 8, wherein receiving the SOAP message, processing at least a portion of the SOAP message, and annotating a message object are each performed by a single computing device, and wherein the method further includes:

at the single computing device, determining that the property indicates that the property should not persist upon serialization of the SOAP message;

removing the property annotated to the message object; and

transmitting the message object over a wire after removal of the property

from the message object.

11. The system of claim 10, wherein transmitting the message object comprises:

formatting at least a portion of the message as a transport stream by providing a SOAP model capable of streaming at least the body portion; and

loading the header portion of the SOAP message into memory, such that random access to the header portion is preserved while the body portion is streamed.