《Windows Communication Foundation Unleashed》：深入解析与开发指南

需积分: 4 71 浏览量更新于2024-08-01 收藏 11.11MB PDF 举报

《Windows Communication Foundation (WCF) 解密》是一本由 Craig McMurtry、Marc Mercuri、Nigel Watling 和 Matt Winkler 合著的专业书籍，由 Sams Publishing 出版。该书针对Windows Communication Foundation (WCF)，Microsoft 的一款核心.NET框架组件，全面深入地讲解了其设计、架构和开发实践。WCF 是为了简化企业级服务的创建和集成，通过提供统一的接口和服务协议，支持多种通信模式，如HTTP、TCP、UDP等，以及各种消息传递架构。书中内容涵盖了以下几个关键知识点： 1. **概述与背景**：介绍了WCF的发展历程和在.NET框架中的重要性，以及它如何作为企业服务总线的角色，实现应用程序之间的松耦合和跨平台通信。 2. **设计原则**：讨论了WCF的设计理念，包括可扩展性、安全性和可配置性，以及如何通过配置和服务契约来定制服务行为。 3. **基础概念**：涵盖服务合同（Service Contracts）、绑定（Bindings）和终结点（Endpoints）等基础知识，这些是构建WCF服务的基础组件。 4. **传输与协议**：详细解释了WCF支持的不同传输协议，如HTTP、TCP、NetNamedPipe等，并展示了如何选择合适的协议来满足不同的性能和安全需求。 5. **消息传递**：介绍如何使用WCF进行异步通信和消息队列，包括 MSMQ、Azure Service Bus等消息传递机制。 6. **安全性**：探讨了WCF的安全模型，包括身份验证、授权、加密和访问控制，以及如何保护服务和数据。 7. **服务生命周期管理**：讲解了服务的启动、暂停、停止以及故障恢复策略。 8. **服务发现与路由**：介绍了如何利用WCF的动态服务发现和路由功能，实现自动的服务查找和负载均衡。 9. **分布式事务和协调**：对于需要跨多个服务处理复杂业务流程的应用，讨论了WCF如何与ADO.NET Entity Framework等工具结合，支持分布式事务和协调。 10. **自定义解决方案**：书中还包含了许多实用示例和最佳实践，帮助读者理解和构建自己的WCF解决方案。 11. **附录和索引**：提供了详细的参考信息，包括API参考、配置示例和索引，便于查阅和进一步研究。《Windows Communication Foundation Unleashed》是一本实用的指南，不仅适合WCF开发者深入理解技术细节，也对希望升级技能或解决企业级服务架构问题的IT专业人员大有裨益。版权和法律声明确保了读者合法使用本书的信息，同时明确指出书中的责任和免责声明。

Tell Us What You Think!

As the reader of this book, you are our most important critic and commentator. We value

your opinion and want to know what we’re doing right, what we could do better, what

areas you’d like to see us publish in, and any other words of wisdom you’re willing to

pass our way.

As a senior acquisitions editor for Sams, I welcome your comments. You can fax, email, or

write me directly to let me know what you did or didn’t like about this book—as well as

what we can do to make our books stronger.

Please note that I cannot help you with technical problems related to the topic of this book, and

that due to the high volume of mail I receive, I might not be able to reply to every message.

When you write, please be sure to include this book’s title and author as well as your

name and phone or fax number. I will carefully review your comments and share them

with the author and editors who worked on the book.

Email: feedback@samspublishing.com

Fax: (317) 428-3310

Mail: Neil Rowe, Senior Acquisitions Editor

Sams Publishing

800 East 96th Street

Indianapolis, IN 46240 USA

Foreword

I started working on the Windows Communication Foundation in 2001 (then known as

“Indigo”), when we were a small team—I was perhaps the 20th person to join. In my

tenure on the team, I served as lead program manager for storage, manageability, reliable

messaging, and queuing. The team had a great vision of facilitating the next generation of

Web services by creating a foundation for Web services that could be practically applied to

a breadth of distributing computing problems. We wanted to ensure that Web services

could be implemented for businesses that enable secure communication—confidentiality,

signing, federation—so distributed computing customers could use Web services for

communication in the real world. We wanted to make sure that Web services could partic-

ipate in transactions in the ACID model, ensuring that practical interactions with data-

driven systems, or with which “all or nothing” computing is essential. We wanted to

ensure that Web services could be written in a way that lossiness of the WAN didn’t

inhibit development of meaningful distributed applications—where you could actually

count on messages getting where you sent them, and in the order you sent them. In

retrospect, these “basic plumbing” goals seem almost quaint, but in 2001 we accepted, for

the most part, the need to “do it ourselves” when building distributed systems.

We also understood that most computing environments are heterogeneous, with systems

from many vendors coexisting with each other, so we wanted to ensure interoperability

through great technical web service standards. We made a deep commitment to interoper-

ability, and executed relentlessly on that commitment. WS-Security, WS-

AtomicTransactions, WS-ReliableMessaging, WS-Management, WS-Policy, WS-Transfer,

WS-Eventing and others were essential for broad interoperability at the “basic plumbing”

level—but none existed when we kicked off this project (all were made possible in greater

or lesser part by colleagues on the WCF team). Looking back, we might say “Of course we

want to work with other systems with broadly accepted composable Web service stan-

dards”—but again, in 2001 this was a lofty goal.

We wanted to support a single programming model so developers wouldn’t face a new

learning curve if they wanted to shift from message-oriented to remote procedural para-

digms, or to go from TCP to HTTP or queuing protocols such as MSMQ. In the face of

.Net Remoting, ASMX, Sockets, MSMQ, and other programming models, a unified API to

accomplish what any of its predecessors could seemed difficult—we were trying to forge

one from many. We wanted to support extensibility, so that each new message exchange

pattern, protocol, or encryption mechanism wouldn’t force yet-another programming

paradigm.

For my part as a lead program manager, I helped champion manageability—the idea that

anything that should be left to the IT pro (protocol du jour, encryption mechanisms,

service addresses, monitoring aspects, and so on), could be. Here again we had lofty

goals—we wanted best-of-breed tracing, intrinsic monitoring and control of applications

built with WCF, ease of use through great configuration and tracing tools, and integration

with all the Windows management assets through WMI. The goal was simply that appli-

cations built with WCF would be intrinsically more manageable with less effort than

those built on other frameworks.

And perhaps most ambitiously, we wanted it to be easy and fun to build great distributed

applications for use in the real world. We wanted it to intuitively lead developers to build

applications that followed the best practices of distributed systems. As Steve Swartz, one

of the greatest champions of “easy and fun” told me, our goal was to build a framework

such that “if you set a ball at the top of a hill and let it roll down, it would just naturally

stop in a place where you had a well factored Service that helped you avoid all the

mistakes distributed systems developers have made in the last 20 years.”

So how did we do? Looking at the finished product that shipped as part of .Net 3.0 in

Vista and on the Web, I think we actually did pretty darned well. WCF is a unified, exten-

sible framework that does in fact help you build secure, reliable, interoperable, manage-

able real world distributed applications in a unified framework that is, by gum, actually

fun (well, at least for those of us who enjoy programming). It took us six years, but we hit

all our key goals. In fact, I like the product so well that my NEW job is focused on build-

ing new products for Microsoft to sell that bet entirely on the facilities that WCF provides

(and I’m having a blast). This book is on every developer and PM’s shelf in the team—it is

the “go to” reference for those of us who either provide or consume Web services in the

product—which is basically all of us (including several developers and PMs who actually

helped build WCF!).

A few words about Craig. Craig and I met while he was serving as the technical evangelist

for WCF. His energy and enthusiasm for the product was infectious—he was a great cham-

pion of the vision. About 90% of the time, when a question came up about “Can we

support that scenario?” Craig would chime in with “Oh yeah, I did that last week—here’s

the prototype.” In his role, he was able to see the “gestalt” of the product in a way that

those of us who were heads down on specific features didn’t. His candid feedback, techni-

cal depth, and enthusiasm were instrumental in making WCF what it is today. I believe

his comprehensive knowledge of and enthusiasm for WCF shines through every chapter—

I am sure you’ll find the book as enjoyable, enlightening, and plain useful as we do here

on our team.

—Alex Weinert

Group Program Manager, Microsoft Corporation

Introduction

The Windows Communication Foundation, which was code-named Indigo, is a technol-

ogy that allows pieces of software to communicate with one another. There are many

other such technologies, including the Component Object Model and Distributed

Component Object Model, Remote Method Invocation, Microsoft Message Queuing

(MSMQ), and WebSphere MQ. Each of those works well in a particular scenario, not so

well in others, and is of no use at all in some cases. The Windows Communication

Foundation is meant to work well in any circumstance in which a Microsoft .NET assem-

bly must exchange data with any other software entity. In fact, the Windows

Communication Foundation is meant to always be the very best option. Its performance

is at least on par with that of any other alternative and is usually better; it offers at least

as many features and probably several more. It is certainly always the easiest solution to

program.

Concretely, the Windows Communication Foundation consists of a small number of .NET

libraries with several new sets of classes that it adds to the Microsoft .NET Framework

class library, for use with the second version, the 2.0 version, of the .NET Common

Language Runtime. It also adds some facilities for hosting Windows Communication

Foundation solutions to the 5.1 and later versions of Internet Information Services (IIS),

the web server built into Windows operating systems.

The Windows Communication Foundation is distributed free of charge as part of a set

that includes several other technologies, including the Windows Presentation Foundation,

which was code-named Avalon, Windows CardSpace, which was code-named InfoCard,

and the Windows Workflow Foundation. Prior to its release, that group of technologies

was called WinFX, but it was renamed the .NET Framework 3.0 in June 2006. Despite that

name, the .NET Framework 3.0 is still primarily just a collection of classes added to the

.NET Framework 2.0 for use with the 2.0 version of the .NET Common Language

Runtime, along with some enhancements to the Windows operating system, as shown in

Figure I.1.

One can install the .NET Framework 3.0 on Windows XP Service Pack 2, Windows Server

2003, and Windows Server 2003 R2. The runtime components are pre-installed on

Windows Vista. On the successor to Windows Server 2003, which is code-named Windows

Server “Longhorn,” one can add the .NET Framework 3.0 via the Server Configuration

Wizard. Only a very small number of features of the .NET Framework 3.0 will be available

exclusively on Windows Vista and later operating systems.

This book does not serve as an encyclopedic reference to the Windows Communication

Foundation. Instead, it provides the understanding and knowledge required for most

practical applications of the technology.

剩余718页未读，继续阅读

mikedd

粉丝: 0
资源: 3

《Windows Communication Foundation Unleashed》：深入解析与开发指南

Windows Communication Foundation Unleashed

Windows.Communication.Foundation.Unleashed(WCF揭密part1)源代码

Windows.Communication.Foundation.Unleashed(WCF揭密part2)源代码

wcf揭秘英文版 wcf揭秘英文版

[WCF系列] WCF 经典原版著作 合集

Silverlight 2 Unleashed

ASP.NET Unleashed

WPF 4 unleashed

[WCF系列] WCF 揭秘 (英文版)

Windows Communication Foundation (WCF) 开发权威指南

最新资源

[WCF系列] WCF 经典原版著作合集