WCF服务编程：Juval Lowy的第三版指南

5星 · 超过95%的资源需积分: 10 191 浏览量更新于2024-07-25 收藏 10.32MB PDF 举报

"Programming WCF Services (Third Edition)" by Juval Lowy 本书是WCF（Windows Communication Foundation）领域的经典著作，作者Juval Lowy是一位知名的软件架构师和技术专家，他在书中详细介绍了WCF服务的编程技术。WCF是微软.NET框架的一部分，用于构建分布式应用程序，它提供了统一的服务模型，可以实现不同平台之间的通信。 WCF学习必备书的称号表明，无论你是初学者还是有经验的开发者，这本书都能提供深入的理解和实用的指导。书中涵盖了WCF的核心概念，包括服务合同、绑定、行为、运行时组件和服务托管。服务合同定义了服务提供的操作；绑定定义了服务如何与客户端通信；行为则影响服务的行为和配置；运行时组件是WCF内部处理服务请求的机制；服务托管则涉及服务在何处以及如何启动和运行。在第三版中，作者可能更新了内容以反映.NET框架的最新发展，包括对.NET Framework 4.x及更高版本的支持，以及与Azure云服务的集成。此外，可能会讨论WCF与RESTful服务、Web API以及服务安全性和身份验证的结合使用。书中详细讲解了如何设计和实现服务，包括创建服务接口、定义数据契约、实现服务操作、配置服务主机，以及测试和调试服务。同时，作者还可能探讨了WCF的高级主题，如事务、消息队列、持久性、可靠消息传递和错误处理。通过实例和实战演练，读者将学会如何创建、部署和管理WCF服务，理解服务生命周期，以及如何利用WCF实现企业级的解决方案。此外，书中的内容不仅限于理论，还强调了最佳实践和陷阱避免，帮助开发者在实际项目中有效应用WCF。总而言之，《Programming WCF Services (Third Edition)》是一本全面的指南，旨在帮助读者掌握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页未读，继续阅读

freetalent

粉丝: 0

WCF服务编程：Juval Lowy的第三版指南

[WCF服务编程].(Programming.WCF.Services).Juval.Lowy.文字版.pdf.7z

Programming WCF Services全书含源码

[WCF] WCF 服务编程 第1版 (英文版)

如何在西门子Opcenter Execution Core的8A.1版本中结合WCFServices实现生产调度流程的优化？

如何利用西门子MES的Opcenter Execution Core和WCFServices优化生产调度流程？请结合8A.1版本的特点。

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

在西门子Opcenter Execution Core 8A.1版本中，如何通过WCFServices功能实现生产调度流程的自动化和优化？

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

C#中怎么通过wcf把一个wpf上的Grid网格绘制到另一个wpf上

uni.uploadFile调用wcf

最新资源

[WCF] WCF 服务编程第1版 (英文版)