.NET Web Services: Architecture and Implementation

You can design a Web service from the viewpoint of the client or from the viewpoint of the service. Both are valid in terms of...

Right after interoperability, the questions I hear the most about designing Web services deal with performance. This isn't surprising, because XML is textual and obviously...

One of the key reasons to use Web service technologies in a distributed application is interoperability. Just as you can use HTTP and HTML browsers...

One of the most critical design decisions you can make is dealing with how to version Web services. As with many other distributed technologies, it's...

To help not only with versioning, but also with designing a loosely coupled system, try as much as possible to write code that is independent...

Another design tip to keep in mind is to use .NET's caching features. There are two related features in ASP.NET Web Services that enable the...

There are more techniques for designing and implementing Web services than this book can possibly cover. But here are the highlights: Think about performance from day...

Throughout this book, we've examined the Web services architecture. This includes baseline specifications—such as XML, SOAP, and WSDL—and more advanced specifications that provide for advanced...