Most Helpful Customer Reviews
|
|
15 of 16 people found the following review helpful:
4.0 out of 5 stars
Nicely done, excellent code examples, November 3, 2004
I think the book will appeal to two groups. Those people who want to use a web service from a company described in the book and people who are interested in learning about some real world applications using web services. The number of companies discussed are few, but they are the big players. I liked the discussion of web services in general and how they can be (and are) used in real world applications.
This book shows you - with copious amounts of code - how to use various services provided by real companies right away. For me, this book was a great way to gather ideas about different approaches to provide and interact with web services. It does a great job at proving how simple web services really are.
Although web services are not language-specific, the book and all the examples are in Java. You should be pretty comfortable with Java, Tomcat, and similar technologies to be able to get the examples working. The companies/web services discussed are: Amazon, eBay, Google, FedEx, PayPal, CDDB. It also discusses interacting with bloggers.
|
|
|
18 of 21 people found the following review helpful:
4.0 out of 5 stars
Short, sweet, practical web service examples, November 6, 2004
This book is mainly code applied to several web services case studies. There is an introductory segment at the beginning which has some nice illustrations. After that the book uses a combination of Java code and screenshots to demonstrate eight example uses of web services. The most handy one, in my opinion, is the News Aggegator, which uses web services to retrieve information from sites like Amazon. Then it turns that information into RSS so that you can retrieve it with your news reader.
There is a lot more code than text in this book. If you learn well by looking at code then this book should work for you. This book is a little looser than the O'Reilly standard. There are more screenshots than usual, the UML graphics are not as well done as usual, and the code is not as well annotated. That being said, it's a fun and informative read that finally injects a little reality into the web services hype.
|
|
|
11 of 12 people found the following review helpful:
4.0 out of 5 stars
entirely adequate -- useful even -- level headed, December 7, 2004
Real World Web Services starts with a recitation of the history of the internet, then
discuses some of the web service offerings currently available, including Java code
for programming remote procdure calls to them, then concludes with a short visionary
chapter in which the author relaxes his prohibition against opinionating and speculating.
The discussion of N-tier architecture, and the checklist of things to be careful about,
when considering deployment of a web service, and the nod to capitalist realities -- if
you don't have a business plan, you're just playing around, not like that's bad or anything,
but the angels aren't going to kidnap you and issue you your very own beach house -- are
most useful, and come from a solid perpective.
How do you choose between raw CGI, SOAP, REST, binary, and XML? What are
the good points and drawbacks of each? Real World Web Services discusses these
generalities. Is UDDI worth the trouble when WDSL already comes with commercial
SOAP development tools? Real world web services will tell you, probably not.
As a developer of web services since before the term had been coined, I tend to
use the traditional Comman Gateway Interface key/value pairs data declaration
method for passing data to my web services rather than XML. Iverson touches on
this legacy method, in a box, on page 99, while discussing PayPal's Instant Payment
Notification system: "Using a simple HTTP request/response is perhaps the most basic,
universal web service. It works with virtually every programming language and requires no
special configuration to use. It's a classic case of the simple solution being the best
solution."
There is no further discussion of simple HTTP request/response, also known as
"common gateway interface." Perhaps he wishes to discourage reinventing too
many wheels, when the available ones (SOAP) take care of a mess of details.
I suppose the plentiful Java example code will be welcome to fans of Iverson's previous
books on Jakarta and J2EE
|
|
|
Most Recent Customer Reviews
|