Expert Service-OrientedArchitecture in C#Using the Web Services Enhancements 2.0JEFFREY HASAN3901fm_final.qxd 6/30/04 2:50 PM Page i Expert Service-Oriented Architecture in C#: Using the Web ServicesEnhancements 2.0Copyright © 2004 by Jeffrey HasanAll rights reserved. No part of this work may be reproduced or transmitted in any form or by anymeans, electronic or mechanical, including photocopying, recording, or by any information storageor retrieval system, without the prior written permission of the copyright owner and the publisher.ISBN (pbk): 1-59059-390-1Printed and bound in the United States of America 987654321Trademarked names may appear in this book. Rather than use a trademark symbol with everyoccurrence of a trademarked name, we use the names only in an editorial fashion and to thebenefit of the trademark owner, with no intention of infringement of the trademark.Lead Editor: Ewan BuckinghamTechnical Reviewers: Mauricio Duran, Fernando GutierrezEditorial Board: Steve Anglin, Dan Appleman, Ewan Buckingham, Gary Cornell, Tony Davis,Jason Gilmore, Chris Mills, Steve Rycroft, Dominic Shakeshaft, Jim Sumser, Karen Watterson,Gavin Wray, John ZukowskiProject Manager: Tracy Brown CollinsCopy Edit Manager: Nicole LeClercCopy Editor: Ami KnoxProduction Manager: Kari BrooksCompositor: Linda Weidemann, Wolf Creek PressProofreader: Sachi GuzmanIndexer: Rebecca PlunkettCover Designer: Kurt KramesManufacturing Manager: Tom DebolskiDistributed to the book trade in the United States by Springer-Verlag New York, Inc., 175 FifthAvenue, New York, NY 10010 and outside the United States by Springer-Verlag GmbH & Co. KG,Tiergartenstr. 17, 69112 Heidelberg, Germany.In the United States: phone 1-800-SPRINGER, e-mail orders@springer-ny.com, or visit http://www.springer-ny.com. Outside the United States: fax +49 6221 345229, e-mail orders@springer.de, orvisit http://www.springer.de.For information on translations, please contact Apress directly at 2560 Ninth Street, Suite 219,Berkeley, CA 94710. Phone 510-549-5930, fax 510-549-5939, e-mail info@apress.com, or visithttp://www.apress.com.The information in this book is distributed on an “as is” basis, without warranty. Although everyprecaution has been taken in the preparation of this work, neither the author(s) nor Apress shallhave any liability to any person or entity with respect to any loss or damage caused or alleged tobe caused directly or indirectly by the information contained in this work.The source code for this book is available to readers athttp://www.apress.comin the Downloadssection.3901fm_final.qxd 6/30/04 2:50 PM Page ii Nothing is really work unless you would rather be doing something else.JAMES BARRIESCOTTISH DRAMATIST(1860–1937)3901fm_final.qxd 6/30/04 2:50 PM Page iii 3901fm_final.qxd 6/30/04 2:50 PM Page iv Contents at a GlanceForeword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiAbout the Author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiAbout the Technical Reviewers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xivAcknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiChapter 1 Introducing Service-Oriented Architecture . . . . . . . . .1Chapter 2 The Web Services Description Language . . . . . . . . . . . .19THÔNG BÁO TUYỂN DỤNG Công ty TNHH Siêu Nhật Thanh (SNT) nhà phân phối thức sản phẩm thuộc lĩnh vực Công Nghệ Thông Tin Truyền Thông nhà sản xuất hàng đầu giới Với 08 năm hoạt động, SNT giành vị trí quan trọng thị trường ICT Việt Nam Để đáp ứng cho việc phát triển nguồn nhân lực công ty dành cho việc triển khai, vận hành khai thác tốt dự án giai đoạn từ 2016 - 2020, cần tuyển vị trí nhân sau đây: VỊ TRÍ TUYỂN DỤNG: Kỹ sư Dịch vụ (Junior/ Senior Services Engineer) Số lượng: 02 người (1: Junior, 1: Senior) Thời gian: Từ đến hết ngày 31/ 03 /2017 MÔ TẢ CÔNG VIỆC: Tham gia nghiên cứu sản phẩm/giải pháp theo yêu cầu trưởng phận; Kiểm tra chất lượng & thử nghiệm thiết bị điện tử, truyền hình; Viết tài liệu cho sản phẩm (đặc tính kỹ thuật, hướng dẫn sử dụng); Triển khai dự án hỗ trợ xử lý cố liên quan đến sản phẩm/ giải pháp; Tìm hiểu tài liệu thiết bị/giải pháp khách hàng để đưa hỗ trợ tư vấn dịch vụ cho phận kinh doanh; Đào tạo huấn luyện đội ngũ kỹ thuật viên/SVTT công ty; YÊU CẦU: Tốt nghiệp Đại Học, chuyên ngành Kỹ Thuật ngành Điện Tử-Viễn Thông, CNTT, … Ưu tiên Sinh Viên Kỹ Thuật trường (vị trí Junior) Nắm vững kiến thức chuyên ngành; Driver/Firmware cho hệ thống; Sử dụng số phần mềm thiết kế thông dụng Autocad, Protel, Có kỹ tìm kiếm tài liệu/sản phẩm, đọc hiểu tài liệu kỹ thuật chuyên ngành; Đọc, viết Tiếng Anh; Thật thà, cẩn trọng có tinh thần trách nhiệm cao; QUYỀN LỢI Nhân viên có lực tốt ký hợp đồng thức chưa hết thời gian thử việc (60 ngày) Môi trường làm việc động, sáng tạo, thân thiện, hội thăng tiến đào tạo thêm để nâng cao nghiệp vụ chuyên môn Mức lương triệu – triệu + Phụ cấp & thưởng (khi ký HĐLĐ thức); Tăng lương theo hiệu công tác công ty thực đầy đủ chế độ dành cho người lao động theo qui định pháp luật hành (BHXH, BHYT, BHTN, ngày nghĩ năm, du lịch, ) Có lương tháng thứ 13 theo qui định công ty thưởng năm theo kết hoạt động toàn công ty Nơi làm việc: Tp Hồ Chí Minh & công tác vị trí khách hàng Chú ý: Hồ sơ xin việc bao gồm: Đơn xin việc lý lịch cá nhân (tiếng Việt tiếng Anh), ưu tiên bảng viết tay 01 ảnh pho-to chứng liên quan (nếu có), không cần công chứng Hồ sơ dự tuyển xin gửi đến: Công ty TNHH Siêu Nhật Thanh B0.23 Đường CC2, KCN Tân Bình, P Sơn Kỳ, Q Tân Phú, Tp Hồ Chí Minh Attn.: Phụ trách Nhân Sự Dự tuyển vị trí: Kỹ sư Dịch Vụ (ghi rõ Junior hay Senior) Mọi thông tin công việc xin liên hệ: Bà: Nguyễn Thị Hương Lan – Trưởng P HC-Nhân Sự Tel: (84-8) 62647077 Mobile : 0913195902 Email: lan.nth@snt.vn Mọi thông tin SNT: xin vui lòng tham khảo www.snt.com.vn COM and .NET Component Services Copyright © 2001 O'Reilly & Associates, Inc. All rights reserved. Printed in the United States of America. Published by O'Reilly & Associates, Inc., 101 Morris Street, Sebastopol, CA 95472. Nutshell Handbook, the Nutshell Handbook logo, and the O'Reilly logo are registered trademarks of O'Reilly & Associates, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O'Reilly & Associates, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps. The association between eels and COM and .NET is a trademark of O'Reilly & Associates, Inc. While every precaution has been taken in the preparation of this book, the publisher assumes no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. Foreword I first ran into COM+ back in 1996. In those days, I was working as a Common Object Request Broker Architecture (CORBA) consultant and was fresh out of IBM, where I had been heavily involved in IBM's original CORBA implementation. CORBA was the first of the architectures that we might describe today as Distributed Component architectures, which set the stage for both COM/DCOM in the Microsoft space and RMI/IIOP in the Java space. Back then, I was interested in a particularly knotty problem related to distributed component architectures. Systems built with such architectures had a characteristic performance pattern. They could handle large numbers of transactions, as long as those transactions originated from a small number of clients. So, for example, 5,000 transactions per minute divided between 5 clients worked fine. But when those same 5,000 transactions per minute were split among 1,000 clients, each processing 5 transactions per minute, the systems choked. This was odd, I thought. Why should 5 clients, each processing 1,000 transactions per minute, be fundamentally different than 1,000 clients, each processing 5 transactions per minute? What is the difference between the first 5,000 transactions per minute and the second? Copyright Table of Contents Index Full Description About the Author Reviews Reader reviews Errata COM and .NET Component Services Juval Löwy Publisher: O'Reilly First Edition September 2001 ISBN: 0-596-00103-7, 384 pages COM & .NET Component Services provides both traditional COM programmers and new .NET component developers with the information they need to begin developing applications that take full advantage of COM+ services. This book focuses on COM+ services, including support for transactions, queued components, events, concurrency management, and security. Page 1 of 23810/3/2002file://F:\Documents%20and%20Settings\Administrator\Local%20Settings\Temp\Rar$EX0 . Distributed component architectures, as they existed in 1996, dictated a one-to-one relationship between clients and component instances. The business logic of such architectures is in the component instances. And it is the business logic that makes transactional requests of transactional resources, such as the database. In order to make transactional requests, the component instances require expensive resources, such as database connections. We run out of steam (i.e., transactional throughput) when one of two things happen: we overload the system with transactional requests or we run out of resources (e.g., database connections). Clearly, going from 5 clients, each making 1,000 transactional requests per minute, to 1,000 clients, each making 5 transactional requests per minute, has no Update on National Hurricane Center Products and Services for 2017 New or recent changes to NOAA’s National Hurricane Center (NHC) products include: 1) Storm Surge Watch/Warning becomes operational Beginning with the 2017 hurricane season, the National Weather Service (NWS) will issue storm surge watches and warnings to highlight areas along the Gulf and Atlantic coasts of the continental United States that have a significant risk of life-threatening inundation from a tropical cyclone, subtropical cyclone, post-tropical cyclone, or a potential tropical cyclone Storm surge is often the greatest threat to life and property from a tropical cyclone, and it doesn’t always occur at the same times or locations as a storm’s hazardous winds In addition, while in most cases coastal residents can remain in their homes (or in a secure structure nearby) and be safe from a tropical cyclone’s winds, evacuations are generally needed to keep people safe from storm surge Having separate warnings for these two hazards will save lives by better identifying the specific tropical cyclone hazards communities face, and by enhancing public response to instructions from local officials The storm surge watch/warning areas are determined by a collaborative process between the NHC and local NWS Weather Forecast Offices (WFOs) The primary objective guidance will be P-Surge, an ensemble-based probabilistic system driven by the SLOSH model, the latest NHC official tropical cyclone forecast, and the typical historical errors associated with NHC forecasts Forecaster confidence, continuity from advisory to advisory, and other subjective factors will also help determine the areas placed under a watch or warning A graphic (e.g., Figure 1) depicting the watch and warning areas will be available on the NHC website (www.hurricanes.gov) whenever these watches/warnings are in effect Below is an example of the graphic: In addition to the graphic, the watch and warning areas will be included in Hurricane Local Statements issued by NWS Forecast Offices, and in the NHC Public Advisory The definitions for the new storm surge watch and warning are: Storm Surge Watch: The possibility of life-threatening inundation from rising water moving inland from the shoreline somewhere within the specified area, generally within 48 hours, in association with an ongoing or potential tropical cyclone, a subtropical cyclone, or a post-tropical cyclone The watch may be issued earlier when other conditions, such as the onset of tropical storm-force winds, are expected to limit the time available to take protective actions for surge (e.g., evacuations) The watch may also be issued for locations not expected to receive life-threatening inundation, but which could potentially be isolated by inundation in adjacent areas Storm Surge Warning: The danger of life-threatening inundation from rising water moving inland from the shoreline somewhere within the specified area, generally within 36 hours, in association with an ongoing or potential tropical cyclone, a subtropical cyclone, or a post-tropical cyclone The warning may be issued earlier when other conditions, such as the onset of tropical stormforce winds, are expected to limit the time available to take protective actions for surge (e.g., evacuations) The warning may also be issued for locations not expected to receive lifethreatening inundation, but which could potentially be isolated by inundation in adjacent areas The Potential Storm Surge Flooding Map, which became operational in 2016, will continue to be issued in 2017 This product provides quantitative information on the storm surge hazard associated with tropical cyclones, highlighting geographical areas where