WCF服务编程实战第三版：深入详解

5星 · 超过95%的资源需积分: 9 127 浏览量更新于2024-07-23 收藏 6.05MB PDF 举报

《编程WCF服务第三版》(Programming WCF Services 3rd Edition) 是由Juval Löwy所著的一本专业IT技术书籍，主要关注Windows Communication Foundation (WCF) 的深度开发与实践。WCF是微软.NET框架中的一个重要组成部分，旨在提供一种统一的、基于协议的、面向服务的架构，使得应用程序能够跨越网络进行可靠、安全和高性能的通信。本书的核心知识点围绕WCF服务的设计、实现、配置以及高级特性展开，包括但不限于以下几个方面： 1. **WCF基础**：介绍WCF的核心概念，如服务契约（Service Contracts）、接口（Interfaces）、消息类型（Message Types）和绑定（Bindings）。这部分内容将帮助读者理解如何定义服务的接口和交互模式。 2. **配置与部署**：详细讲解如何配置WCF服务端和客户端，包括主机（Hosts）、行为（Behaviors）、安全（Security）和性能优化策略。这部分内容对于实际部署和管理生产环境中的服务至关重要。 3. **服务模式与架构**：涵盖各种服务模式，如单体应用服务（Single-Instance）、多实例（Multiple Instances）、并发处理（Concurrency）以及分布式服务（Duplex and Callbacks）。读者可以学习如何根据业务需求选择合适的架构。 4. **RESTful服务**：随着API设计趋势的变化，书中会介绍如何利用WCF实现RESTful风格的服务，包括HTTP协议的使用和媒体类型（Media Types）的处理。 5. **高级主题**：涉及WCF的扩展性、故障恢复、异步处理、服务总线（Service Bus）集成等内容，以及如何利用WCF与其他.NET框架组件（如Entity Framework）协同工作。 6. **案例研究与最佳实践**：书中提供了丰富的代码示例和实战案例，展示如何解决实际问题，并分享作者在项目中的经验教训。作为第三版，本书在前两版的基础上进行了更新，以反映WCF在.NET 4.x和.NET Core框架中的最新进展，确保内容与时俱进。此外，它还包含了对WCF在云计算和微服务架构中的应用探讨，有助于开发者紧跟技术潮流。《编程WCF服务第三版》是一本全面且实用的指南，无论你是WCF初学者还是有经验的开发者，都能从中获取到提升技能和解决实际问题的宝贵知识。通过阅读和实践书中的内容，读者将能熟练地构建、管理和维护高效、可扩展的网络服务。

Designing the Bridge 518

Transaction Configuration 519

Service-Side Configuration 520

Client-Side Configuration 522

10. Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525

Authentication 525

Authorization 526

Transfer Security 527

Transfer Security Modes 527

Transfer Security Mode Configuration 529

Transport Security and Credentials 532

Message Security and Credentials 533

Identity Management 533

Overall Policy 534

Scenario-Driven Approach 534

Intranet Application Scenario 535

Securing the Intranet Bindings 536

Constraining Message Protection 543

Authentication 544

Identities 547

The Security Call Context 548

Impersonation 550

Authorization 558

Identity Management 563

Callbacks 564

Internet Application Scenario 566

Securing the Internet Bindings 566

Message Protection 568

Authentication 572

Using Windows Credentials 574

Using the ASP.NET Providers 575

Identity Management 584

Business-to-Business Application Scenario 585

Securing the Business-to-Business Bindings 585

Authentication 586

Authorization 589

Identity Management 590

Host Security Configuration 591

Anonymous Application Scenario 591

Securing the Anonymous Bindings 591

Authentication 592

Authorization 592

xiv | Table of Contents

Foreword

When Juval Löwy asked me to write the foreword for the first edition of this book, I

was working in a Community Program Manager role for the brand-new Windows

Communication Foundation (WCF) framework at Microsoft. WCF was the result of

a multiyear effort to write a unified communication framework for Windows. It was

also the result of a multiyear effort to create an interoperable messaging standards

framework centered around XML and the SOAP envelope model, with a common

model for addressing; a transport-independent abstraction for session management and

ordered delivery semantics; and a common model for message and session protection,

for federated authentication and authorization, and for many more capabilities. This

industry-wide standardization effort is still in progress with Microsoft and partners

across the industry, refining and updating this common messaging framework (sum-

marily nicknamed “WS-*”), more than 10 years after the SOAP 1.1 specification was

submitted as a note to W3C, which started this process.

As I write the foreword to the new edition, I’m filling an Architect role on the Windows

Azure AppFabric team at Microsoft. More precisely, I’m contributing to the architec-

ture of the service bus, a service offering that’s part of the Windows Azure Platform

and which Juval covers in Chapter 11 and the appendixes of this book. The way I

commonly describe the effort of building a commercial web services infrastructure, like

the service bus or its sibling service, Windows Azure AppFabric Access Control, is to

use the familiar iceberg analogy. The “above the water” features that the customers get

to interact with on the public protocol and API surface area make up a relatively small

portion of the overall effort. The rest, all the things beneath the waterline, quite closely

resembles a large-scale, mission-critical Enterprise application infrastructure—with the

special quality and challenge of running on a public cloud-based infrastructure.

When you create a Windows Azure account, your data and the provisioning jobs run

through WCF SOAP services. When you create a new service namespace in our system,

the messages flow between data centers using WCF SOAP services, creating resources

in the places where you ask for them to be created. Monitoring happens via WCF SOAP

services; diagnostics happens via WCF SOAP services; billing data collection, consol-

idation, and handoff happens using WCF SOAP services.

xvii

As people providing a public web service infrastructure, we’re looking to provide

equally capable messaging-centric and REST protocol heads and resource projections

across the infrastructure. Because of concerns about broad reach into browsers and

devices, the prioritization often plays out in a way that the REST protocol heads for the

public protocol surface area win out and get built first—and mostly on top of the HTTP

web programming model provided by WCF. However, there has never been any serious

debate or question in cross-team engineering discussions about the interfaces between

the various subsystems under the waterline not being SOAP-based endpoints built on

WCF. Everyone already went into the room with the assumption that they would be.

Building the backbone systems for a cross-team effort at Microsoft with several hundred

engineers and an investment volume the size of the Windows Azure Platform is at or

beyond the complexity level of many mission-critical Enterprise systems. Running such

a system and upgrading or changing parts of such a system in flight and without down-

time is not only complex, it’s an art form. You need loose coupling between subsystems,

you need a lot of flexibility and extensibility, and you need to have a clear notion of

what that other system is going to accept and return in terms of messages. What I keep

finding is that once you confront a “simpler” communications model with real-world

requirements of the sort we’ve got on the Windows Azure backbone, you almost in-

evitably end up reinventing the wheel at the protocol level and you increasingly make

the life of implementers harder.

WCF is a great technology because it deals with the complexity of flexibly intercon-

necting applications. It’s great because you can build SOAP services, building the

backbone of your systems that can interoperate with other services on other platforms

with similarly capable web services stacks, such as those built by Oracle/Sun, IBM, or

the Apache Foundation. It’s great because it allows you to build the “broad-reach”

HTTP/REST resource projection surface of your system on the same foundation.

The book you have in your hands is rightfully “the book” about the Windows Com-

munication Foundation. Continuously improving our skills at architecting and build-

ing distributed business applications is a passion that Juval and I share.

This book is going to help you learn about the “distributed” part—how to hook stuff

together and how to do so securely, reliably, and in a loosely coupled fashion—all from

Juval Löwy, one of the most prominent distributed systems experts in the world today.

xviii | Foreword

剩余909页未读，继续阅读

erental

粉丝: 7
资源: 1

WCF服务编程实战第三版：深入详解

Programming WCF Services 3rd Edition(WCF服务编程第3版）含源代码

Programming WCF Services, 3rd Edition

visual studio 创建wcf服务库和wcf服务应用程序有什么区别

c# webconfig wcf https

wcf和http文件传输练习

vs2022 wcf使用

WCF路由实现（SOAP）

C#中wcf进程间通信

vs wcf 更新接口

WCF和java的区别

最新资源