Simultaneous API exposure for messages

• US 7,925,710 B2
• Filed: 08/31/2006
• Issued: 04/12/2011
• Est. Priority Date: 01/31/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Swartz, Stephen T., Purdy, Douglas M., Osovetsky, Eugene, Pharies, Stefan H., Box, Donald F., Wolf, Kenneth D., Christensen, Erik B., Vernal, Michael S.
• Primary Examiner(s): Follansbee; John
• Assistant Examiner(s): Daftuar; Saket K
• Application Number:
  US11/469,433
• Publication Number:
  US 20070198989A1
• Time in Patent Office: 1,685 Days
• Field of Search: 709/220, 709/217, 709/227, 709/228, 709/229, 709202-203, 709206-207, 709/209, 709/230, 709/245, 707/10, 707/104, 707/1, 719/313, 717114-118, 370/352, 370/389, 370/428, 715/FOR.215, 715/FOR.227, 715/FOR.233, 715/FOR.240
• 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 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. A method, performed in a distributed messaging system, of simultaneously exposing a message infoset as both an XML view, which allows the message infoset to be accessed as XML data, and a Typed view, which allows the message infoset to be accessed as a typed data object, such that at least a portion of the message infoset can be written using an XML API, through which the message infoset is accessed as a typed data object, and read using a Typed API, through which the message infoset is accessed as XML data, in order to efficiently process values of the message infoset, the method comprising:

receiving an XML message infoset comprising a SOAP object written using the XML API, the message infoset including a common set of XML headers that each enclose a value, the XML headers being exposed as both XML and typed properties such that the value enclosed by each XML header is simultaneously exposed as both an XML view and a Typed view such that at least a portion of the XML message infoset can be accessed using the XML API and the Typed API in order to efficiently process values of the message infoset wherein the XML message infoset is accessible by;

creating a common language infrastructure object, using the XML API, by;

(1) identifying an index to the header using an XML name encapsulating the value of the header;

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

(3) passing the header to the read operation for creating a typed representation of the header; and

by;

directly accessing the value using the Typed API as if the value were the value of a typed property of a Common Language Infrastructure object without first identifying an index of the XML header or creating an XMLReader for the XML header; and

retrieving the values using the Typed API, which can access the typed properties without regard to how the message infoset is encoded using XML.

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

9. The method of claim 1 wherein the implementation of the Common Language Infrastructure is the Common Language Runtime.

3. A method, performed in a distributed messaging system, of simultaneously exposing a message infoset as both an XML view, which allows the message infoset to be accessed as XML data, and a Typed view, which allows the message infoset to be accessed as a typed data object, such that at least a portion of the message infoset can be written using a Typed API, through which the message infoset is accessed as a typed data object, and read using an XML API, through which the message infoset is accessed as XML data, in order to efficiently process values of the message infoset, the method comprising:

creating an XML message infoset comprising a SOAP object that includes a common set of XML headers that each enclose a value, the XML headers being exposed as both XML and typed properties such that the value enclosed by each XML header is simultaneously exposed as both an XML view and a Typed view such that at least a portion of the message infoset can be accessed using a Typed API and using an XML API in order to efficiently process values of the message infoset, wherein the value enclosed by each XML header is written to the XML header by;

directly writing the value using the Typed API as if the XML header were an object in an implementation of the Common Language Infrastructure, wherein the value of each XML header is written using the Typed API; and

retrieving the values using the XML API, which reads the XML headers by;

(1) identifying an index to the header using an XML name encapsulating the value of the header;

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

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

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

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

6. In a distributed messaging system, a computer program product comprising:

one or more computer storage media, wherein the computer storage media excludes signals, having stored thereon computer executable instructions that, when executed by a processor, cause the distributed messaging system to perform steps for simultaneously exposing a message infoset, comprising a SOAP message, as both an XML view, which allows the message infoset to be accessed as XML data, and a Typed view, which allows the message infoset to be accessed as a typed data object, such that at least a portion of the message infoset can be written using a Typed API, through which the message infoset is accessed as a typed data object, and read using an XML API, through which the message infoset is accessed as XML data, in order to efficiently process values of the message infoset, the steps comprising;

creating an XML message infoset that includes a common set of XML headers that each enclose a value, the XML headers being exposed as both XML and typed properties such that the value enclosed by each XML header is written to the XML header by;

directly writing the value using the Typed API as if the XML header were an object in an implementation of the Common Language Infrastructure, wherein the value of each XML header is written using the Typed API; and

retrieving the values using the XML API, which reads the XML headers by;

(1) identifying an index to the header using an XML name encapsulating the value of the header;

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

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

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

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