 See larger picture | .NET Web Services: Architecture and Implementation (Microsoft .NET Development Series)
by
Keith Ballinger
- Addison-Wesley ProfessionalList Price: $54.99
Price at Amazon.com: $34.64
(Save
37%)
 Availability: Usually ships in 24 hours
Shipping rates and policies |
- Average Customer Review:
Based on
17
reviews.
- Amazon.com Sales Rank: 240477
|
Featured Customer Reviews  Very clear introduction to MS web service technologies,
September 15, 2006
Note this is an older book, so I imagine quite a few things have changed since it was published - although the code generated by the toolkit I just downloaded is compatable with what I see in the book so far. Also, as others have mentioned, this book does not contain complex, real-world examples.
If you are looking for an intro/overview of MS WS technologies, and are willing to hit the web for updates, this book is a good choice. This is a horrible book.,
March 01, 2006
The language is bad too: on page 72, "There's a convenient Add Web Reference dialog box...exactly for that kind of thing." What do you mean by "that kind of thing"? Are you writing a professional book or just an IM chat message? Besides, the discussion of creating clients with VS .NET is horribly shallow.
Avoid this book.
Substandard: shallow, few examples, MANY errors!!!,
May 22, 2005 This is one of the most disappointing books I have ever read. I have read a few books in the ".NET Development Series" before and have come to expect solid, easy to grasp, and useful information. This books fails on almost every account.
The explanations are inadequate. The author uses a lot of time to explain the obvious, while failing to explain more complex topics.
The language is really, really bad. An example: "Of course, there are many other applications of routing as well. As well, I fully expect that this specification will evolve over time."!!??
Maybe the most annoying thing about the book is all the dreadful typos and inconsistencies. I have never seen anything like it, and I cannot believe that anyone ever did any proofreading of this book. For example on page 35 he describes a very simple example of a Web Service, a class "TestClass" with one method "Add". On the next page is the image from Internet Explorer which shows what you see when you type the URL of the service on the server, the class is suddenly named "POClass". Later when he describes the SOAP Message for the service it is for another class altogether with a method "HelloWorld"???!!! In this example, it is easy to figure out what is wrong, and it is more annoying than anything else, but in other places where the material is not so easy to understand, the errors are harder to ignore.
Finally and maybe most importantly, the author fails to give any motivation for a lot of the things he does. For example, he describes how one in different ways (by using attributes, etc) can change the format of the soap messages for the service. However, he doesn't say a word about why one should prefer one format for the other.It is not a reference. It is only an overview.,
January 17, 2005 Hi,
In the first chapters, where the Keith describes the protocols and underlying technologies of the XML WebServices, the reader gets more question marks in his head only. The explanations are very short. Actually there is no explanation, the author recommends to see the specifications foreach topic. For many things even there isn't any information.
As you read the book, you get the feeling that the author knows everything about web services, but he is not willing to show everything. Maybe he didn't have much time for the book, or had other things to do.
Kaan Ozturk
No practical information to actually get you started,
October 28, 2004 The author jumps around various topics, and constantly refers to SOAP standard section 5 or 7 in his descriptions. It looks as if he expect the readers to be fully conversant with the nuts and bolts of SOAP spec, and we all know this is a tall order.
Worst of all, he failed to put together even a single real world app to illustrate the best way to make use of web services, TODAY.
He talks about Web service technology as if the tech is an end onto itself.
Don't buy it, you know you don't have time to toil thru a dorky tech spec discussion, esp. when the spec itself is getting out-of-date very fast.
You might also be interested in these items...
|
|