Microsoft Technology Licensing, LLC

Eugene Osovetsky

Erik B Christensen

Kenneth David Wolf

Donald F Box

Stephen Jared Maine

Stephen T Swartz

Michael Steven Vernal

Douglas M Purdy

Natasha Harish Jethanandani

Stefan H Pharies

Sowmyanarayanan K Srinivasan

Krishnan R Rangachari

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.

Simultaneous API exposure for messages

Converting data to an appropriate format for use with a service. An example method is illustrated where a message including data expressed using dynamic language data expressions is received. The dynamic language data expressions include a tree structure organization for the data. The data expressed using dynamic language data expressions is expressed in an XML data structure. The XML data structure preserves the original tree structure organization for the data.

Complete mapping between the XML infoset and dynamic language data expressions

Growing community of inventors

Bellevue, WA, United States of America

Eugene Osovetsky