Microsoft Technology Licensing, LLC

Ryan Thomas Sturgell

Michael Marucheck

Erik B Christensen

Stephen James Millet

David Wortendyke

Stephen T Swartz

Michael Steven Vernal

Kenneth David Wolf

Michael James Coulson

Stefan Harrington Pharies

Eric Kenneth Zinda

Douglas M Purdy

Natasha Harish Jethanandani

Jesus Ruiz-Scougall

Jesus Ruiz Scougall

Alex DeJarnett

Christopher G Kaler

Giovanni Moises Della-Libera

James Ernest Johnson

Tirunelveli R Vishwanath

Lance Olson

Richard Douglas Hill

Umesh Madan

Stefan R Batres

John David Doty

Craig Andrew Critchley

Vijay Gajjala

Uday Sooryakant Hegde

Elliot Lee Waingold

Krishnan Srinivasan

Yann Christensen

Matthew Thomas Tavis

Tomasz Janczuk

Geary L Eppley

David Edwin Levin

Shy Cohen

Max A Feingold

Richard Dievendorff

David Owen Driver

Siddhartha Puri

Saurab Nog

Aaron Stern

Anastasios Kasiolas

Douglas A Walter

Kapil Gupta

Vipul A Modi

Sowmyanarayanan K Srinivasan

Scott Christopher Seely

Mohammad Makarechian

Evgeny Osovetsky

Jonathan T Wheeler

Alexander Martin DeJarnatt

Michael Thomas Dice

Yaniv Pessach

Mauro Ottaviani

Erin Honeycutt

Chaitanya Dutt Upadhyay

Alfred M Lee, Iv

Yasser Shohoud

Eugene Shvets

Anand Rjagopalan

Mohamed-Hany Essam Ramadan

Serge Sverdlov

Vaithiakingam B Balayoghan

Vaithialingam B Balayogan

Alex DeJarnatt

The present invention extends to using Simple Object Access Protocol ('SOAP') to exchange typed objects, such as, for example, parameters for invoking methods. A computer system accesses typed object parameters corresponding to a typed object. The typed object is annotated with one or more message contract attributes of a message contract model defining a mapping between typed object parameters and corresponding SOAP elements. The computer system utilizes the message contract attributes to map the typed object parameters into a SOAP element and inserts the SOAP element into a SOAP envelope. A receiving computer system accessing the SOAP element and utilizes the message contract attributes to map the SOAP element back into the typed object parameters.

Flexibly transferring typed application data

The present invention extends utilizing abstract descriptions to generate, exchange, and configure service and client runtimes. A computer system parses compiled code and potentially optional configuration information for implementing a service and converts the compiled code and any configuration information into an abstract service description. The abstract service description can then be converted into code document object model and service configuration information or exported as metadata. A corresponding service runtime can be initiated by calling a service initializer included in the abstract service description. The code document object model and configuration information and/or metadata can be transferred to another computer system. The other computer system can utilize the code document object model and configuration information and/or import the metadata to facilitate initialization of a compatible channel for communicating with the service runtime.

Utilizing abstract descriptions to generate, exchange, and configure service and client runtimes

The present invention extends to mapping between object oriented and service oriented representations of a distributed application. A computer system accesses an annotated object oriented representation of a service, which is annotated with service description attributes mapping included objects to corresponding service oriented elements in a service oriented representation of the service. The computer system identifies a service description attribute that annotates an object of the annotated object oriented representation. The computer system maps the object to a corresponding service oriented element in accordance with service description information contained in the identified service description attribute. The computer system outputs a channel object configured to implements behaviors and data formats described in the service oriented representations. The computer system initiates a channel that is compatible with behaviors and data formats of the service.

Mapping between object oriented and service oriented representations of a distributed application

A web services namespace pertains to an infrastructure for enabling creation of a wide variety of applications. The infrastructure provides a foundation for building message-based applications of various scale and complexity. The infrastructure or framework provides APIs for basic messaging, secure messaging, reliable messaging and transacted messaging. In some embodiments, the associated APIs are factored into a hierarchy of namespaces in a manner that balances utility, usability, extensibility and versionability.

Interface infrastructure for creating and interacting with web services

Methods, systems, and computer program products for abstracting processing layers within a messaging infrastructure so that changes or enhancements can be made to the infrastructure while retaining existing functionality. Message transport implementations are abstracted within a message layer, allowing other layers within the infrastructure to interact with messages in a more structured fashion, largely independent of message transport. Transport examples include named pipes, Transmission Control Protocol (TCP), HyperText Transfer Protocol (HTTP), Simple Mail Transfer Protocol (SMTP), etc. A channel layer above the message layer abstracts message exchange implementations, allowing other layers within the infrastructure to send and receive messages in a more structured fashion, largely independent of the message exchange semantics of a specific implementation. Message exchange examples include datagrams, dialogs, monologs, queues, and the like. Above the channel layer and message layer, a service layer abstracts the binding implementations that bind message exchange implementations to user code implementations.

Transmitting and receiving messages through a customizable communication channel and programming model

Growing community of inventors

Seattle, WA, United States of America

Ryan Thomas Sturgell