"WCF Technology Insider" translation 16: Part 1th _ 4th Chapter _WCF101: Overview

4th Chapter: WCF101

Overview

The WCF framework is a complex framework, and its complexity stems from the fact that, on the abstraction layer, a message framework must adapt to the constant updating and refinement of industry standards. In the WCF design phase, soap and ws-* are considered to be the future mainstream message structures and protocols. None of the architects in charge of WCF would have imagined that JSON would have today's status. But they do understand the fact that WCF must be well compatible and adaptable to those new message structures and transmissions, just as WCF is now. So Microsoft has designed a highly scalable and adaptable WCF that can meet today's messaging needs as well as future unpredictable new requirements. The result of these efforts is a complex platform that is easy to use but is somewhat incomprehensible on the whole

Everyone who has designed a large framework (framework) can prove that designing, building, testing, and maintaining this framework is a daunting task. I have designed, discussed, and built several frameworks to understand how difficult this is. When designing a framework, Alan Kay's famous remark ^{[old Xu 1]}"Simple things should be simple, complex things can be successful" should be the first principle. When looking at WCF today, I think Microsoft has succeeded in achieving this quote by simplifying many complex things, even in the long run. This is not to say that I think WCF is perfect, without errors, but that, as a complete product, WCF is thoughtful and well-designed.

One of the WCF core requirements is exposing an object model to the developer, which can be compatible with all transports and protocols. The embodiment of the example is that the architects of the WCF team want the code that sends messages over TCP/IP to look very similar to the code that sends messages through MSMQ. This feature has several advantages. First, it means that the platform does not force developers to learn about the various object models of different transports and protocols. In fact, developers who understand WCF objects and execute models can implement support for different transports and protocols in their application systems. Second, it means that with WCF's successful support for new transmissions, protocols, and features, developers do not need to learn new ways of communicating in order to develop new functionality in the system. Instead, they can use the communication mechanisms that already exist in the WCF framework.

Because of these types of requirements, the WCF architecture consists of a number of interwoven layers. Over time, I've found that to fully understand one layer of any WCF infrastructure, you need to first understand some of the concepts associated with each layer in the WCF infrastructure. The purpose of this chapter is to introduce the main levels of WCF applications and to lay a solid foundation for further study of these layers in the later chapters of this book.

"Old Xu Notes"

1. Simple things should is simple and complex things should be Possible,alan is one of the inventors of the Smalltalk object-oriented programming environment language, and one of the founders of object-oriented programming ideas, he still notes The first designer of the computer and the architect of the modern Windows GUI (architect).