SIMULTANEOUS API EXPOSURE FOR MESSAGES

• US 20070198989A1
• Filed: 08/31/2006
• Published: 08/23/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., Swartz, Stephen T., Wolf, Kenneth D., Purdy, Douglas M., Osovetsky, Eugene, Christensen, Erik B., Vernal, Michael S., Pharies, Stefan H.
• Granted Patent: US 7,925,710 B2
• Time in Patent Office: Days
• US Class Current: 719/313
• 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 a message object that simultaneously exposes an XML view and Type view for a message infoset. In this embodiment, interaction with a message can occur using either an XML or Type application program interface (API), which are synced. More specifically, embodiments herein provide or expose a common set of headers (e.g., SOAP headers) as “typed” properties (e.g., CLR properties), which allow for getting and/or setting a value thereof In other words, the Type API reads/writes values for typed properties without regard to how the message is encoded with XML. Moreover, the two APIs are synced such that a value can be set using one API and retrieved using the other. For example, an XML API may be used as a writing mechanism for interacting with a value, while the Type API can read that same value, and vise-versa.

Claims

1. In a distributed messaging system, a method of simultaneously exposing a message infoset as both an XML view and a Type view such that at least a portion of the message infoset can be written using an XML API and read using a Type API in order to efficiently process values of the message infoset, the method comprising:

receiving a message infoset written using an XML writer, the message infoset including a common set of headers that exposes one or more values as both XML and typed properties; and

retrieving the one or more values using a Typed API, which can read one or more of the type properties without regard to how the message is encoded using XML.

2. The method of claim 1, wherein the typed properties are URI string values.

3. The method of claim 1, wherein the infoset is a SOAP object.

4. In a distributed messaging system, a method of simultaneously exposing a message infoset as both an XML view and a Type view such that at least a portion of the message infoset can be written using a Type API and read using an XML API in order to efficiently process values of the message infoset, the method comprising:

receiving a message infoset that includes a common set of headers that exposes one or more values as both XML and typed properties, wherein the type properties are set using a Typed API; and

retrieving the one or more values using an XML reader, which reads the type properties as encoded XML.

5. The method of claim 4, wherein the typed properties are URI string values.

6. The method of claim 4, wherein the infoset is a SOAP object.

7. The method of claim 4, wherein the retrieving of the one or more values further comprises:

identifying an index to a header using a XML name encapsulating the one or more values;

retrieving an XML dictionary reader specific to the header that includes a read operation; and

passing the header to the read operation for creating a typed representation of the header.

8. The method of claim 7, wherein the XML name is a qualified name including a name and namespace.

9. In a distributed messaging system, a computer program product for implementing a method of simultaneously exposing a message infoset as both an XML view and a Type view such that at least a portion of the message infoset can be written using a Type API and read using an XML API in order to efficiently process values of the message infoset, 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 message infoset that includes a common set of headers that exposes one or more values as both XML and typed properties, wherein the type properties are set using a Typed API; and

retrieve the one or more values using an XML reader, which reads the type properties as encoded XML.

10. The computer program product of claim 9, wherein the typed properties are URI string values.

11. The computer program product of claim 9, wherein the infoset is a SOAP object.

12. The computer program product of claim 9, wherein the computer program product further comprising executable instructions that cause the distributed messaging system to perform the following when retrieving the one or more values:

identify an index to a header using a XML name encapsulating the one or more values;

retrieve an XML dictionary reader specific to the header that includes a read operation; and

pass the header to the read operation for creating a typed representation of the header.

13. The computer program product of claim 9, wherein the XML name is a qualified name including a name and namespace.