suspending, resuming, or canceling an instance. Protocols in the following table enable communication for WCF. Protocol name Description Short name 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, which 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, 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 nodes. This
Conceptual Schema Definition File Format Describes the structure and semantics of the Conceptual Schema Definition Language (CSDL) for the Entity Data Model (EDM). Entity Data Model for Data Services Packaging Format Specifies the Entity Data Model for Data Services Packaging Format (EDMX), an XML-based file format that serves as the packaging format for the service metadata of a data service. Protocols in the following table are used in ASP.NET. Protocol name Description Short 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.
Examples Example 1 (.NET Remoting): Two-Way Method Invocation Using SOAP Over HTTP The .NET Remoting framework is one of the main categories of .NET protocols. This example illustrates the two-way method invocation that is mapped to the use case. In this example, the client invokes a method on the server, and the server responds with the result, which is an object of the address class. For the detailed example, see section 4.2. Initial System State General requirements as set forth in section 1.5. The server must be configured to respond with the address. Sequence of Events The following diagram shows the sequence of events for two-way method invocation. Figure : Sequence diagram for two-way method invocation The client requests an address from the server. The server responds with the address. Final System State The client receives the requested address. Client and server can communicate further by using the same or a different contract. Example 2 (WCF): Hello World This code example illustrates a simple request and response that is mapped to the use case. The service defines the following service contract. [ServiceContract] public interface IHelloWorldService { [OperationContract] string SayHello(string name); } The server implementation returns the string World!!" when the client sends the sayHello message with "World!!" as its input argument. public class HelloWorldService : IHelloWorldService { public string SayHello(string name) { return string.Format("Hello, {0}", name); } }
Index A Actors 37 37 48 33 15 36 B 6 C 48 64 48 35 35 35 35 35 15 Considerations 48 48 D 47 Dependencies 35 35 Design intent 37 47 44 36 38 E 35 48 Examples hello world 49 50 system state 51 50 reliable messaging with flow control 55 56 system state 60 56 TCP as transport 51 52 system 55 52 retrieve a single entity using the JSON format 60 60 system state 61 60 two-way method invocation using SOAP over HTTP 49 49 system state 49 49 Extensibility 62 48 35 F Functional 15 requirements 29 28 26 30 15 Windows 16 15 15 15 G 8 H 48 Hello world 49 50 system state 51 50 I 62 48 12 36 6 M
62 N 44 O Overview 29 28 26 30 33 15 Windows 16 15 P 36 63 R 12 Reliable messaging with flow control 55 56 system state 60 56 TCP as transport 51 52 system 55 52 6 Requirements 29 48 28 48 26 30 15 36 Windows 16 15 Retrieve a single entity the JSON format 60 60 system state 61 60 S 48 Stakeholders 36 36 System 15 dependencies 35 35 35 48 overview 6 6 33 requirements 29 28 26 30 15 Windows 16 15 use cases 37 47 44 36 38 15 35 35 35 48 33 15 System use 37 36 T 33 64 Two-way method invocation SOAP over HTTP 49 49 system 49 49 U Use cases 37 47 44 36 38 V Versioning 62 48