Abstract: A computerized system that implements a type system can process one or more XML documents that comprise unknown schema elements, which may not correlate within one or more types in the type system. In one implementation, for example, a computer system receives one or more XML document feeds and deserializes only those schema elements that correlate with one or more system types. The computer system further passes the unknown schema elements to a buffer. An application program, such as an XML reader, can extract the unknown schema elements from the buffer as appropriate. In one implementation, for example, the application program maintains its own types separately from the system types. The application program can then correlate its application-specific types with the buffered schema elements to deserialize and process the buffered schema elements.

Abstract: The transformation of data between binary data and hierarchical data, such as might be processed by an Infoset Processor. When data is received from a network in binary format, the transformation module transforms the binary data into a hierarchical data representation of the binary data, and then provides the transformed data to message processors (e.g., Infoset processors) that understand the hierarchical schema. The transformation module may also transform hierarchical data into binary data for transmission on a network.

Abstract: Namespace for continuation-based runtime. Some embodiments described herein are directed to a framework using continuation based runtime namespaces that pertain to an infrastructure for enabling the creation of a wide variety of continuation-based programs that perform a wide-array of tasks. The infrastructure provides a foundation for building continuation-based, declarative applications of various scale and complexity. In some embodiments, the associated application programming interfaces (APIs) are factored into a hierarchy of namespaces in a manner that balances utility, usability, extensibility, and versionability.

Abstract: A system for aggregating context information for messages. The system includes a context container. The context container associates names with context values and metadata for context entries. The system further includes a network protocol component configured to read messages from a network transport, an encoder component configured translate messages from a raw format into a canonical message format. The canonical message format is an enveloped message containing an application payload and message metadata. The context container is associated with a message in the canonical format.

Abstract: Technologies for conversations between various parties, the conversations including context information that can be persisted to maintain the conversation when the parties or the communications media they communicate over operate intermittently. In such a conversation, any party can embed its view of the context into a message and any party can send the next message regardless of role and regardless of the underlying network, transport, or application message exchange pattern. Such technologies provide for durable services.

Abstract: The present invention extends to methods, systems, and computer program products for dispatching client requests to appropriate server-side methods. When a client request is received, a Web server refers to a service contract framework that maps URI paths and HTTP methods to corresponding server implemented methods. A server implemented method corresponding to a URI path and/or an HTTP method included in the client request is identified. The server implemented method is invoked to process the client request message. Accordingly, embodiments of the invention provide a uniform mechanism to dispatch HTTP requests to designated server implemented methods based solely on URI path and HTTP method. That is, an HTTP request can be dispatched to a designated server implemented method without having to include additional dispatch metadata within the HTTP request (e.g., in a SOAP envelope).

Abstract: Encoding and/or decoding of messages. On the encoding end, a composite encoder encodes message from an internal format that is used by internal system components into an external format. However, the composite encoder may encode the outgoing messages into different external formats on a per-message basis. For incoming message, a composite decoder decodes incoming messages from any one of a plurality of external formats into the internal format also on a per-message basis. A per-message report mechanism permits internal system components and the encoding/decoding components to communicate information regarding the encoding or decoding on a per message basis. This permits a higher level of collaboration and complexity in the encoding and decoding process.

Abstract: The transformation of data between binary data and hierarchical data, such as might be processed by an Infoset Processor. When data is received from a network in binary format, the transformation module transforms the binary data into a hierarchical data representation of the binary data, and then provides the transformed data to message processors (e.g., Infoset processors) that understand the hierarchical schema. The transformation module may also transform hierarchical data into binary data for transmission on a network.

Abstract: The present invention extends to methods, systems, and computer program products for dispatching client requests to appropriate server-side methods. When a client request is received, a Web server refers to a service contract framework that maps URI paths and HTTP methods to corresponding server implemented methods. A server implemented method corresponding to a URI path and/or an HTTP method included in the client request is identified. The server implemented method is invoked to process the client request message. Accordingly, embodiments of the invention provide a uniform mechanism to dispatch HTTP requests to designated server implemented methods based solely on URI path and HTTP method. That is, an HTTP request can be dispatched to a designated server implemented method without having to include additional dispatch metadata within the HTTP request (e.g., in a SOAP envelope).

Abstract: A computerized system that implements a type system can process one or more XML documents that comprise unknown schema elements, which may not correlate within one or more types in the type system. In one implementation, for example, a computer system receives one or more XML document feeds and deserializes only those schema elements that correlate with one or more system types. The computer system further passes the unknown schema elements to a buffer. An application program, such as an XML reader, can extract the unknown schema elements from the buffer as appropriate. In one implementation, for example, the application program maintains its own types separately from the system types. The application program can then correlate its application-specific types with the buffered schema elements to deserialize and process the buffered schema elements.