WCF post-transfer series (10): Message Processing core Abstract: WCF is a communication framework and can also be seen as a basic framework for message processing or transmission, it can receive, process, or construct a message based on the data specified by the client and send the message to the target endpoint. In this process, everything is centered around the "message. While providing a unified programming model for the message processing architecture, this article describes how to configure a message to support various versions of soap and WS-Addressing, or without soap and WS-Addressing, and how to control the message status.
WCF post-transfer series (9): Deep-channel Programming Model Part 2-instance Summary: essentially, WCF is a communication service framework that allows us to use different transmission protocols, different message encoding formats are used to interact with different WS-* series specifications. All these details are handled by the channel stack. In the WCF topic series (8): Deep Channel Programming Model Part 1-design, I have a deep understanding of the channel model in WCF. In this article, I will explain through examples how the server receives messages and how the client sends messages in the channel model.
WCF post-transfer series (8): Deep-channel Programming Model Part 1-Design Abstract: essentially, WCF is a communication service framework that allows us to use different transmission protocols, different message encoding formats are used to interact with different WS-* series specifications. All these details are handled by the channel stack. To simplify these processes, two models are provided in WCF: one is the application programming model for developers and the other is the channel model for communication. for developers, it is enough to understand the application programming model without involving the channel model. However, the necessary learning of the channel model allows us to truly understand the concept of "communication" in WCF, understand the entire architecture of WCF, so as to build a more robust WCF Service or expand the WCF framework. In this article, we will have a deep understanding of how the channel model in WCF is designed.
WCF post-transfer series (7): How messages are transmitted and bound to Part 2 Abstract: In the WCF topic series (6): How messages are transmitted and bound to part 1, I mentioned that binding is composed of binding elements. Each binding element is used to describe an aspect of the communication mode between the endpoint and the client. Each binding element represents a processing step when sending or receiving messages; during runtime, the binding element creates necessary channels and listeners to generate the stack of outgoing and incoming channels. This article describes how to bind a message in the second part. It describes in detail the various built-in binding elements of WCF, the order between binding elements, and how to create a custom binding element.
WCF post-transfer series (6): How to transfer a message binding part 1 Abstract: each service endpoint contains an address, a binding, and a contract Contract. The contract specifies available operations, and the binding specifies how to communicate with the service. The address specifies the location of the service to be searched. In the first five articles of the WCF topic series, the detailed addressing in WCF is learned in depth; starting from this article, I will have a deep understanding of B in the classic "ABC", that is, binding, its principles, how to use binding communication, and how to publish it in metadata.
WCF post-transfer series (5): goes deep into the WCF addressing Part 5-Logical Address and physical address summary: In WCF, each service endpoint is associated with two addresses, A logical address and a physical address are the target address of the SOAP message, that is, the "to" address mentioned more than once, and the physical address is the address actually listened by the WCF listener. In WCF, the logical address is called the endpoint address, while the physical address is called the listening address listenuri. This article describes in detail the physical and logical addresses in WCF, and how to use tcptrace to track soap messages.
WCF post-transfer series (4): Deep-dive into the WCF addressing Part 4-custom message filter Abstract: In the WCF topic series (3): Deep-dive into the WCF addressing Part 3-The message filtering engine article, the message filter engine in WCF is described in detail, including the message filter and filter table. Each endpointdispatcher contains two message filters. The default address filter is endpointaddressmessagefilter, and the default contract filter is actionmessagefilter, these can be changed through behavior. In this article, we will learn how to create a custom message filter and use the custom behavior to change the default filter of endpointdispatcher.
WCF post-transfer series (3): go deep into the WCF addressing Part 3-message filtering engine Abstract: through the introduction in the previous two articles, I have a deep understanding of web service addressing specifications and endpoints in WCF development. In this article, we continue to go deep into the third part of WCF addressing. When a message is passed in, how to determine the matching endpoint is the message filtering engine we will talk about in this article. In WCF, the message filter engine consists of two important components: Filter and filter table.
WCF post-pass series (2): In-depth WCF addressing Part 2-custom addressing header Summary: In the WCF topic series (1): deep in the article titled WCF addressing Part1, we have made some knowledge of the web service addressing specification and understood the two structures of endpoint reference and message header. This specification plays an important role in Web Services, we will often mention this specification later. In this article, we will continue to go deep into the content of WCF addressing, including the endpoint address and custom addressing header in metadata.
WCF post-transfer series (1): Deep-dive into the WCF addressing Part 1-Web Service Addressing Specification Abstract: As we all know, all communication of a WCF Service occurs through the service endpoint, each service endpoint contains an address, a binding, and a contract Contract. The contract specifies available operations, binding specifies how to communicate with the service, and the address specifies the location of the search service, that is, the very classic "ABC ". WCF uses a variety of different communication protocols to provide a flexible mode for public service endpoints and communication with them. In the first part of the WCF topic series, I will discuss the addressing details of endpoints.
Windows Communication Foundation Environment installation Abstract:. NET Framework 3.0 has been released for some time. Should I learn something new if I am too lazy? Start with WCF. As part of. NET Framework 3.0, Windows Communication Foundation (WCF) is release along with Windows Vista, but it does not mean that WCF can be used only in Windows Vista. In addition to Vista, to install the WCF development environment for operating systems, the following conditions must be met:
1. Operating Systems: Windows XP or Windows 2003
2. Because WCF is built on. NET Framework 2.0, you need to install. NET Framework 2.0.
3. Download and install. NET Framework 3.0
Microsoft. NET Framework 3.0 redistributable package
4. To use Visual Studio 2005 for development, you also need to download the vs2005 extension.
Source: http://www.cnblogs.com/Terrylee/category/36734.html
Post-pass a series of learning articles on WCF
