WCF服务编程第三版英文版

需积分: 0 130 浏览量更新于2024-07-26 收藏 7.54MB PDF 举报

"WCF服务编程第三版是Juval Löwy撰写的一本关于Windows Communication Foundation (WCF) 技术的专业书籍。此书主要聚焦于如何利用WCF来构建高效、安全的服务。" Windows Communication Foundation (WCF) 是微软.NET框架的一部分，用于构建和部署可互操作的、面向服务的应用程序。本书的第三版更新了与WCF相关的最新技术和最佳实践，为开发者提供全面的指导，以应对不断变化的技术环境。在WCF中，服务是通过定义合同（Contracts）来描述其功能的，这些合同定义了服务提供的操作和服务期望的交互方式。服务可以通过多种传输协议（如HTTP、TCP等）和消息交换模式（如请求/响应、发布/订阅等）进行通信，这使得WCF具有高度的灵活性和可配置性。 WCF的核心概念包括服务主机（Service Host）、绑定（Bindings）、终结点（Endpoints）、行为（Behaviors）和数据契约（Data Contracts）。服务主机负责承载服务实例，绑定定义了服务与客户端之间的通信细节，终结点是服务暴露给外部世界的地方，行为则影响服务的行为和配置。数据契约定义了服务之间交换的数据结构。本书可能涵盖了创建、配置和部署WCF服务的详细步骤，包括服务的生命周期管理、安全性、事务、可靠性和性能优化等方面。作者Juval Löwy是一位知名的.NET专家，他可能会深入探讨服务的异常处理、错误报告以及服务的测试和调试策略。此外，书中还可能涉及WCF与其他技术的集成，如ASP.NET、SQL Server、Enterprise Service Bus (ESB) 和Web服务标准（如SOAP和WS-*）。对于企业级应用开发，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

Download from Library of Wow! eBook <www.wowebook.com>

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

Download from Library of Wow! eBook <www.wowebook.com>

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

Download from Library of Wow! eBook <www.wowebook.com>

剩余909页未读，继续阅读

weait1988

粉丝: 0
资源: 5

WCF服务编程第三版英文版

wcf服务编程第三版源代码

WCF服务编程第三版 中文 03

WCF服务编程 第三版 带源代码.PDF

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

ASPX VB 如何创建WCF服务

ASPX VBWEB中 如何创建WCF服务

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

visual studio 创建wcf服务库为什么没有svc文件

怎么使用POST 请求WCF服务

如何阻止WCF使用异步编程模型

最新资源

WCF服务编程第三版中文 03

WCF服务编程第三版带源代码.PDF

ASPX VBWEB中如何创建WCF服务