深入学习WCF服务：第3版精华解读

需积分: 10 193 浏览量更新于2024-07-27 收藏 6.05MB PDF 举报

"Programming WCF Services 3rd Edition" 《Programming WCF Services》是 Juval Löwy 编著的关于微软Windows Communication Foundation (WCF) 的第三版指南。这本书深入介绍了如何利用WCF来构建高效、可靠的分布式系统。WCF是微软.NET框架中用于构建面向服务的应用程序的核心技术，它集成了多种通信协议和消息交换模式，为开发人员提供了一站式的解决方案。第四章“实例管理”探讨了在WCF服务中如何控制服务实例的创建、管理和销毁。实例管理是服务性能和可伸缩性的重要因素，因为它直接影响到内存使用和并发处理能力。书中可能涵盖了以下关键知识点： 1. **服务实例化模式**：WCF提供了四种实例化模式——单例（Singleton）、会话实例（Per-Session）、并发实例（Per-Call）和持久化实例（Per-Partition）。每种模式都有其特定的应用场景，例如，单例模式适用于需要全局唯一的服务，而会话实例则适用于需要保持客户端会话状态的情况。 2. **生命周期管理**：理解服务实例何时被创建以及何时被回收，这对于优化服务性能和防止资源泄露至关重要。书中可能讨论了如何配置服务实例的生存时间（Time To Live, TTL）以及超时策略。 3. **线程安全与并发控制**：在多线程环境中，服务实例需要处理多个并发请求。书中可能会讲解如何确保服务代码的线程安全，以及如何调整并发限制以平衡响应时间和系统负载。 4. **服务缓存**：对于性能敏感的服务，可能会涉及到服务实例的缓存策略，以减少实例创建的开销并提高响应速度。 5. **服务宿主和服务托管**：书中可能会介绍如何选择合适的服务宿主（如IIS、自承载或Windows服务），以及如何配置服务的生命周期，以适应不同的部署环境。 6. **服务质量与故障恢复**：实例管理也关系到服务的健壮性和容错性。书中可能探讨了如何处理异常、如何优雅地关闭服务实例，以及如何实现服务的自动重启和故障转移。通过学习《Programming WCF Services 3rd Edition》，开发者可以全面掌握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页未读，继续阅读

metisria

粉丝: 0
资源: 23

深入学习WCF服务：第3版精华解读

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

Programming WCF Services, 3rd Edition

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

c# webconfig wcf https

在 .NET 6 上使用 WCF 服务器端项目

.net core使用服务引用wcf方法的

wcf和http文件传输练习

vs2022 wcf使用

WCF路由实现（SOAP）

C#中wcf进程间通信

最新资源