Figure 1.3 How Web services are discovered. Cons Here are some of the negatives associated with SOAP: nn SOAP standards provided by the W3C are merely recommendations (as are all the standards provided by the W3C), so some companies might drive their own SOAP initiatives and internal standards, mak- ing it difficult or impossible to communicate with processes of dif- ferent application languages and platforms. By doing this, they will be defeating the purpose of interoperability, something that many individuals and groups are hoping the SOAP protocol continues to permit. nn SOAP is still hounded by data type limitations. It still is not possible to pass an unlimited number of data types via HTTP. Most intranet and Internet communications can be accomplished using three or four different data types, but if a special circumstance arose that required a special user-defined data type (UDT), SOAP could not be the solution. nn SOAP can expose a lot of functionality, depending on the code you write. If you write code allowing a Web service to format your C: drive and expose it as a Web service, dont be surprised if it some- day gets called! **The above example depicts non-proxy, the scenario for non-proxy Web service classes only. Server Client Virtual Directory Software Developer Files are downloaded to the client that describe the Web service. HTTP A user requests information about an .asmx Web service. Allows an internal or external client to discover a Web service. .asmx .disco 14 Chapter 1