WCF 3.0实战：服务导向应用设计与开发

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

《编程WCF服务（第三版）》是一本专门针对面向服务的WCF应用程序设计与开发的指南。作者Juval Löwy深入探讨了如何利用WCF内置的功能，如服务托管、实例管理、并发控制、事务处理、离线队列调用、安全性和Windows Azure AppFabric Service Bus等。这本书不仅讲解了WCF编程及其相关系统问题，还关注设计理念和决策背后的原因，旨在使读者成为不仅熟练掌握WCF技术，而且具备软件工程思维的专业人士。在第三版中，作者适应了.NET 4.0的新特性，如托管、发现和配置，更新了内容以涵盖这些变化。AppFabric Service Bus作为本书的重要部分，展示了一种革命性的技术，使得开发者能够构建全新的应用类型。此外，作者分享了两年来的WCF技术进步、实用技巧和助手类，以及对前两版中理念的改进，确保了新内容对第二版读者也具有价值。本书避免过多地涉及WCF的底层实现细节，重点在于展示如何实际运用该技术，以及在各种设计和编程模型之间做出选择。它充分利用了.NET 4.0和服务总线的优势，甚至在某些方面可以视为高级C#教程。作者以软件工程的角度审视每个主题和方面，强调维护性、可扩展性、重用性和生产力的重要性，帮助读者打造高质量、可维护的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

www.it-ebooks.info

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

www.it-ebooks.info

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

www.it-ebooks.info

剩余909页未读，继续阅读

cz_q

粉丝: 0
资源: 9

WCF 3.0实战：服务导向应用设计与开发

Programming WCF Services, 3rd Edition

Programming WCF Services全书含源码

Programming WCF Services, 2nd Edition

ASPX VB 如何创建WCF服务

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

c# webconfig wcf https

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

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

wcf和http文件传输练习

vs2022 wcf使用

最新资源