Revision Summary Date Revision History Revision Comments 5/6/2011 1.0 New Released new document. 6/17/2011 2.0 Major Updated and revised the technical content. 9/23/2011 2.0 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 2.0 None No changes to the meaning, language, or formatting of the technical content. 3/30/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 2.0 None No changes to the meaning, language, or formatting of the technical content.
1/31/2013 2.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 3.0 Major Updated and revised the technical content. 11/14/2013 4.0 Updated and revised the technical content. 2/13/2014 4.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 4.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 5.0 Major Significantly changed the technical content. 9/24/2015 5.1 Minor Clarified the meaning of the technical content. 10/16/2015 5.1 None No changes to the meaning, language, or formatting of the
NET Packet Routing Protocol Specification Defines a SOAP header for indicating that a SOAP message can safely be treated as a packet or datagram. .NET Binary Format: XML Data Structure Defines the .NET Binary Format: XML Data Structure, is a binary format that can represent many XML documents, as specified in [XML1.0]. .NET Binary Format: SOAP Data Structure Defines the .NET Binary Format: SOAP Data Structure, is a new format that is built by extending the format as described in the .NET Binary Format: XML Data Structure, as specified in .NET Binary Format: SOAP Extension Defines the .NET Binary Format: SOAP Extension, which is a new format that is built by extending the format specified in Peer Channel Protocol Specification Used for broadcasting messages over a virtual network of cooperating . This protocol is used to send and receive messages nodes in a named . Peer Channel Custom Resolver Protocol Specification Specifies storage and retrieval of endpoint information for clients that have
service metadata of a . Protocols in the following are used in ASP.NET. Protocol name Description name ASP.NET State Server Protocol Specification Used for interaction between a client application that requires persistent session storage, and an state server that is responsible for storing session state. ASP.NET State Service Database Repository Communications Protocol This protocol specifies an interface for clients to store and retrieve serialized session data. Protocols in the following enable communication for . Protocol name Description Short name .NET Remoting: Core Protocol Specification Specifies a mechanism by which a calling program can invoke a method in a different address space over the network. NET Remoting: Binary Format Data Structure Defines a set of structures that represent object graph or method invocation
Index A Actors 36 36 47 32 14 35 B 11 C 47 63 47 34 34 34 34 34 14 Considerations 47 47 D 46 Dependencies 34 34 Design intent 36 46 43 35 37 E 34 47 Examples hello world 48 49 system state 50 49 reliable messaging with flow control 54 55 system state 59 55 TCP as transport 50 51 system state 54 51 retrieve a single entity the JSON format 59 59 system state 60 59 two-way method invocation using SOAP over HTTP 48 48 system state 48 48 Extensibility 61 47 34 F Functional 14 requirements 28 27 25 29 14 Windows 15 14 14 14 G 5 H 47 Hello world 48 49 system 50 49 I 61 47 8 35 5 M
61 N 43 O Overview 28 27 25 29 32 14 Windows 15 14 P 35 62 R 8 Reliable messaging with flow control 54 55 system state 59 55 TCP as transport 50 51 system state 54 51 11 Requirements 28 47 27 47 25 29 14 35 Windows 15 14 Retrieve a single entity using the JSON format 59 59 system 60 59 S 47 Stakeholders 35 35 System 14 dependencies 34 34 34 47 overview 11 5 32 requirements 28 27 25 29 14 Windows 15 14 use cases 36 46 43 35 37 14 34 34 34 47 32 14 System use cases 36 35 T 32 63 Two-way method invocation SOAP over HTTP 48 48 system state 48 48 U Use 36 46 43 35 37 V Versioning 61 47