MESSAGE OBJECT MODEL

• US 20070180043A1
• Filed: 08/31/2006
• Published: 08/02/2007
• Est. Priority Date: 01/31/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Box, Donald F., Cabrera, Luis Felipe, Wolf, Kenneth D., Christensen, Erik B., Vernal, Michael S., Pharies, Stefan H., Coulson, Michael J., Stern, Aaron
• Granted Patent: US 7,949,720 B2
• Time in Patent Office: Days
• US Class Current: 709/207
• 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 an overall object mode that allows for a single message object to represent multiple messaging formats. A general message object is populated with fields for multiple available messaging formats, which can be appropriately filled with information with fields for both versions 1.1 and 1.2. Depending on which version is being used or desired, the appropriate fields can be populated when creating an instance of the message object. The other fields that do not correspond to that version, however, are left blank.

Claims

1. In a distributed messaging system, a single message class that represents multiple messaging formats comprising:

an envelope that encapsulates contents for a message;

a first set of fields within the envelope configured to include data for elements that correspond to a first message format; and

a second set of fields within the envelope configured to include data for elements that correspond to a second message format, wherein either the first set of fields or the second set of fields can be populated with data to create a message object specific to either the first or second message format, respectively.

2. The single message class of claim 1, wherein one or more of the first set of fields have overlapping properties with the second set of fields.

3. The single message class of claim 1, wherein the single message object model is a SOAP object model, and wherein the first and second sets of fields correspond to a version 1.1 and 1.2 of the SOAP format, respectively.

4. The single message class of claim 1, wherein one or more of the first or second set of fields are included within a header portion, a body portion, or both of the envelope.

5. The single message class of claim 1, wherein one or more of the first or second set of fields are not included within either header or body portions of the envelope.

6. In a distributed messaging system, a method of using a single message class to create a message object for multiple messaging formats, the method comprising:

receiving a request to create a message object that is specific to a first message format;

accessing a message class that includes an envelope, the envelope including a first set of fields configured to include data for elements that correspond to a first message format and a second set of fields configured to include data for elements that correspond to a second message format; and

populating the first set of fields with data for making a message object specific to the first format, wherein one or more fields from the second set of fields are not populated.

7. The method of claim 6, wherein one or more of the first set of fields have overlapping properties with the second set of fields such that at least one of the fields populated with data corresponds to a field from the second set of fields.

8. The method of claim 6, wherein all of the first set of fields are included within the second set of fields.

9. The method of claim 6, wherein the message object is a SOAP object, and wherein the first and second sets of fields correspond to a version 1.1 and 1.2 of the SOAP format, respectively.

10. The method of claim 6, wherein one or more of the first or second set of fields are included within a header portion of the envelope.

11. In a distributed messaging system, a computer program product for implementing a method of using a single message class to create a message object for multiple messaging formats, 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:

receive a request to create a message object that is specific to a first message format.

access a message class that includes an envelope, the envelope including a first set of fields configured to include data for elements that correspond to a first message format and a second set of fields configured to include data for elements that correspond to a second message format; and

populate the first set of fields with data for making a message object specific to the first format, wherein one or more fields from the second set of fields are not populated.

12. The computer program product of claim 11, wherein one or more of the first set of fields have overlapping properties with the second set of fields such that at least one of the fields populated with data corresponds to a field from the second set of fields.

13. The computer program product of claim 11, wherein all of the first set of fields are included within the second set of fields.

14. The computer program product of claim 11, wherein the message object is a SOAP object, and wherein the first and second sets of fields correspond to a version 1.1 and 1.2 of the SOAP format, respectively.

15. The computer program product of claim 11, wherein one or more of the first or second set of fields are included within a header portion of the envelope.