Home > Store

.NET Web Services: Architecture and Implementation

Register your product to gain access to bonus material or receive a coupon.

.NET Web Services: Architecture and Implementation

Book

  • Sorry, this book is no longer in print.
Not for Sale

About

Features

The ultimate Microsoft insider explains how to get the most out of .NET's powerful tools for building Web services

° Ballinger is a key figure on Microsoft's .NET Framework team, and is widely known

° Learn not just how to use .NET to build Web services, but why .NET was built and works the way it does

° Part of the Microsoft .NET Development Series

Description

  • Copyright 2003
  • Dimensions: 7-3/8" x 9-1/4"
  • Pages: 344
  • Edition: 1st
  • Book
  • ISBN-10: 0-321-11359-4
  • ISBN-13: 978-0-321-11359-7

Most books on Web Services have focused on specific technologies, and how to use those class libraries to build services and clients. Some have attempted to give an overview of SOAP and WSDL and other related technologies. This book will address the issue of why Web services exist, and how to create them using Microsoft .NET. As Program Manager for Web Services in Microsoft's .NET Framework group no one is in a better position than Keith to explain why .NET's web services tools were set up the way they are, and how to get the most out of them. Once you understand how implementation and architecture of Web services work in .NET, you'll be better able to take full advantage of .NET's powerful tools. The book features a lot of code and many working examples.

Extras

Related Article

Critical Success Factors for Web Services

Author's Site

Click below for Web Resources related to this title:
Author's Web Site

Sample Content

Online Sample Chapter

Introducing .NET Web Services

Downloadable Sample Chapter

Click below for Sample Chapter(s) related to this title:
Sample Chapter 1

Table of Contents



Foreword.


Preface.


Acknowledgments.


1. Introducing Web Services.

The Problem: Sharing Data.

The Solution: Distributed Application Development.

The Web Architecture.

Defining Web Services.

The Significance of Internet Standards.

The Significance of WSDL.

The Significance of Interoperability.

The Significance of Loose Coupling.

Modular Design.

Message Passing.

Error Handling.

The Web Service Architecture.

The Baseline Specifications of Web Service Architecture.

Summary.



2. XMLWeb Services Standards.

The Basics.

HTTP.

XML and XML Schema.

Standards for XMLWeb Services.

The Protocol: SOAP.

Describing Services with WSDL.

Discovering Services with UDDI.

Other Protocols.

Summary.



3. Creating Web Services with ASP.NET.

Roadmap to ASP.NET Web Services.

Building Servers.

Anatomy of a Web Service.

Building Document-Literal Services.

Building Document-Encoded Services.

Building RPC-Encoded Services.

Building One-Way Services.

Controlling Routing.

Using SOAP Bindings.

Implementing a Server Asynchronously.

Using SOAP Headers.

Returning Errors.

Summary.



4. Creating Web Service Clients.

Creating Clients with the .NET Framework SDK.

Discovery with disco.exe.

WSDL Consumption.

Creating Clients with Visual Studio .NET.

Creating Web Service Clients Manually.

Building Document-Literal Clients.

Building Document-Encoded Clients.

Building RPC-Encoded Clients.

Building One-Way Clients.

Building a Client That Includes Asynchronous Methods.

Handling Errors and SOAP Faults.

Extending and Customizing a Client.

Summary.



5. XML Serialization with .NET.

Overview.

Only Classes with a Public, Default Constructor Will Be Serialized.

Only Public Fields and Properties Will Be Serialized.

Read-Only Fields and Properties Will Not Be Serialized.

Methods and Other Type Information Will Not Be Serialized.

Writing and Reading XML.

Serializing Encoded XML.

Customizing XML Serialization.

The Namespace of Serialized XMLWill Be http://tempuri.org by Default.

Properties and Fields Will Remain in the Same Namespace.

Properties and Fields Will Be Serialized as Elements.

Arrays with XML Serialization.

Serializing Untyped XML.

Creating Classes from Schemas.

XML Serialization and Web Services.

Summary.



6. Extending Web Services.

Soap Extensions.

Description Formatters.

Customizing Transport Information.

Setting Exposed HTTP Properties.

Overriding Proxy Class Behavior.

HTTP Modules.

The Web Services Enhancements for Microsoft .NET.

Summary.



7. Transport Protocols for Web Services.

TCP Communication.

Unreliable Messages with UDP.

SOAP in E-mail: SMTP.

The Web's Transport: HTTP.

The WebClient Class.

The WebRequest Classes.

Summary.



8. Data and Format: XML and XML Schemas.

The Meta-Language.

XML Documents and Namespaces.

Programming with XML and Namespaces.

Streaming XML Processing.

DOM-Based Programming.

Describing XML with Schemas.

Data Types with XML Schema.

Describing the XML Shape.

Programming with Schemas.

Programming Schema-Based XML.

Manipulating XML Schema Documents.

Summary.



9. The Messaging Protocol: SOAP.

Overview of the SOAP Protocol.

Enveloping with SOAP.

Errors with SOAP.

Remote Method Calls with SOAP.

SOAP and HTTP.

Using SOAP to Send Messages.

SOAP Headers and Asynchronous Messaging

Summary.



10. Describing Web Services.

Requirements for Describing Web Services.

The Web Services Description Language.

Extensibility.

Abstraction.

Structure.

Anatomy of WSDL.

Abstract Message Operations.

Concrete Operation Information.

Types.

Messages.

Port Types and Operations.

Bindings.

Services and Ports.

Writing WSDL.

Reading WSDL Documents with .NET.

Extending WSDL.

Web Service Policy.

Summary.



11. Discovering Web Services.

Universal Discovery with UDDI.

The Anatomy of UDDI.

Programmer's API.

WSDL and UDDI.

WS-Inspection.

Anatomy of WS-Inspection.

Ad-Hoc Discovery.

Summary.



12. Messaging with Web Services: WS-Routing, WS-Referral, and DIME.

Logical Names.

Routing Messages.

Message Paths with WS-Routing.

Building WS-Routing Applications.

Dynamic Configuration of SOAP Routers.

DIME.

Anatomy of a DIME Message.

Using DIME with SOAP.

Summary.



13. Securing Web Services with WS-Security.

Security Technologies and Standards.

Authentication.

Confidentiality.

Integrity.

Web Service Security Protocols.

Definitions.

WS-Security.

Summary.



14. Advanced Messaging: Reliability and Sessions.

Sessions.

HTTP Sessions.

Message-Level Sessions.

Message Reliability.

Dialogues and Monologues.

Summary.



15. Designing Web Services.

Performance.

Writing Performance-Oriented Code with .NET.

Message Size and Network Latency.

How Important Is Performance?

Interoperability.

Audience-Centered Design.

Specific SOAP Issues.

Versioning.

Types of Versioning.

Loosely Coupled Architecture and Implementation Versioning.

Namespaces and Versioning.

Using Business Logic.

Caching.

Summary.

Final Thoughts.



Index. 0321113594T01272003

Preface

This book is the result of several years of work. Not just my own personal work (although writing this book has resulted in some late nights), but the hard work and many man years of effort by Microsoft's .NET Framework and XML messaging teams. Several other companies and talented individuals, such as Sam Ruby from IBM have also been critical in taking this technology to the masses.

But it begs the question: why have so many people, and so much money, been poured into this technology? Why is Web services perceived by Microsoft and many others as a huge, and potentially industry changing pieces of work? This book can't possibly give a complete answer. But, I've tried to deliver to you the most important pieces of information I can about Web services, specifically those built with .NET. By doing do, my hope is that you too can see how wonderful this technology is.

Most books on Web Services have focused on specific technologies, and how to use those class libraries to build services and clients. Some of the better ones have attempted to give an overview of SOAP and WSDL and other technologies. What are Web Services? Why do they exist?

I can't answer those questions completely, but I can help people better understand the technology in general, and thereby design and architect better Web Services. I've tried to present the material in a way that makes obvious the reasons for their existence.

Of course, as the Program Manager for Web Services built with Microsoft's .NET Framework, I feel compelled to show off a little. I truly feel that I have helped build the best Web Services technology around. And I think it appropriate to take you through the major features of this technology. Most of the code samples will also use C# and ASP.NET Web Services.

I've tried to design this book to be read front to back, or randomly. Each chapter builds on previous chapters, however most chapters can be read stand-alone and still be useful.

This book consists of 15 chapters. Chapters 1 and 2 explain what Web services are, and the standards that make up the Web services world. Chapter 3 through 6 are an in depth view of how the .NET Framework allows developers to build Web service applications. Chapters 7 through 14 take a step back and drill into the specifications (from HTTP to SOAP to WS-Security) that make up the Web services architecture. Finally, Chapter 15 delivers a few words of advice about architecting and designing Web services applications.



0321113594P10142002

Foreword

Capitalism is the political system based on the recognition of individual rights, including property rights. It is the most productive political system in history. Of all modern industries, the computer business most vividly reflects the benefits of capitalism, and on average it has enjoyed free capital and employment flows and comparatively little regulation. This has made it a home for entrepreneurs and others who think out of the box—innovators in products, marketing, finance, distribution, and corporate organization. The computer business never stands still, and it shatters all conservative estimates of its possibilities.

In 1943, Thomas Watson, then chairman of IBM, said famously, "I think there is a market for maybe five computers on the world market." This made sense, if one's sights were set on the computers of that era: so large and expensive to buy and maintain that only the biggest institutions with the most urgent needs could justify them.

Undaunted, inventors created a stream of new technologies, while entrepreneurs and capitalists built new businesses around them. By the 1960s, led by Remington Rand and others and eventually including IBM, computers became small and cheap enough that businesses could afford to buy a "mainframe" computer for centralized bookkeeping. In the 1970s, inventions in semiconductor technology resulted in the creation of minicomputers. Companies such as DEC decisively broke both the mainframe prices and the centralized model, thereby enabling departments and small groups to own a computer. Then came the integrated circuit, venture capital, Intel, Microsoft, and the personal computer revolution of the 1980s. Forevermore, most computers would be small, inexpensive, and dedicated to individual use. During the 1990s, deregulation unlocked prior investment and innovation in telecommunications. Communication became integrated into the computing fabric, as rapidly dropping bandwidth costs enabled the central computers to take on a new role of serving constellations of personal computers.

Browser-based computing, typified by the World Wide Web, was hugely successful, yet it addressed only one style of computing, namely, remote computers interacting immediately with humans. It did not exploit the possibilities of widely decentralized, personal computing. The inventions that created the World Wide Web—inexpensive computers, cheap communications, extensible protocol formats, and protocol-based, asynchronous, failure-tolerant coupling—have not yet been widely applied to computers that interact, on behalf of humans, directly with other computers.

That is about to change. In 1996, XML (eXtensible Markup Language) was created, and within a few years, it was applied to the invention of SOAP (Simple Object Access Protocol) and XMLWeb Services. Definition: An XML Web service is a computational resource defined solely in terms of the functions it performs, interacting through protocols using XML, SOAP, and WSDL and not presuming the presence of a human as one of the parties to the interaction.

Pursuing fun and profit, business and technical innovators have created invention after exciting invention. You are about to read the story and details of one of the latest, written by a man who played a key role in making XMLWeb Services broadly available.

—Andrew Layman

Index

Click below to download the Index file related to this title:
Index

Updates

Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020