I just finished reading .Net Web Services by Keith Ballinger. Before I started reading this book I felt pretty comfortable with Web Services, but I felt it wouldn't hurt to make sure that I don't have any cracks in my knowledge.
Overall, I really enjoyed this book, it was pretty easy reading, and it was, what I feel, a complete guide to .net web services, and web services in general for that matter. He presented some material in a way that I haven't thought about, and he really had me thinking. For example, he talks about this idea of, "The WSDL First! Movement". The idea is writing WSDL before you write your web service code, and the argument that he makes is that our implementation should not dictate our interface. I never looked at it that way, .Net makes a lot of the web service interface transparent, so it's not intuitive to see it like that.
The bread and butter of this book is definitely chapters 3-6. These chapters really show what .Net has to offer for web services. The chapters cover, creating web services with ASP.NET, creating the clients, xml serialization (this chapter alone is worth the price of the book), and extending web services. The rest of the chapters cover the basics of web services, i.e. SOAP, WSDL, and Xml Schemas. It also covers a few of the WS-... protocols, including WS-Security, WS-Routing, and DIME.
Tomas Restrepo also has a small review of what he thinks about Keith's book. He does point out that there are a few typos and errors in the book, but they are very minor, and it doesn't take away from the quality of this book.
My own small gripe, I wish he mentioned overloading a web method on a web service. I wrote up a post about what happens, but again this is something pretty small. Wow, my first real blog. Let's see how long this goes on for.
12:12:05 PM 
|
|
