Follow Slashdot blog updates by subscribing to our blog RSS feed

 


Forgot your password?
Close
typodupeerror
×
Programming Books Media The Internet Book Reviews IT Technology

Google, Amazon, and Beyond 74

Posted by timothy from the moon-is-next dept.
honestpuck writes "As titles go "Google, Amazon, and Beyond" sounds to me like Buzz Lightyear's latest slogan, but it's actually quite a good book about writing software to consume and provide web services." Read on for honestpuck's review of the book -- it sounds useful for developers on both sides of a web-service transaction, but honestpuck cautions that its value varies with your attachment to Java.
Google, Amazon, and Beyond
author Alexander Nakhimovsky and Tom Myers
pages 314
publisher Apress
rating 6 for most, 8 for Java programmers
reviewer Tony Williams
ISBN 1590591313
summary Good guide to web services for Java programmers

The first two chapters are introductory material, though the authors quickly introduce some code with JavaScript routines to talk to both Google and Amazon. The second of them does a good job explaining the intricacies of DOM and how you use it to build a web page in Java. Then the authors get down to some serious work at using Java, including stand-alone applications and applets, to access web services.

They move fast throughout the book; this is not one to read quickly or without ready access to a computer. That said, the writing is good; the text is understandable and all the code is well explained.

The book covers a wide gamut of techniques and technologies, including SOAP and REST on the query side, and XSLT and XPath on the output side.

Then the book moves on to instructions for offering your own services. This part of the book starts off with WebDAV using Tomcat, though there is a short digression into Java Server Pages before really getting down to the nitty gritty. Finally the book shows how to use WSDL and Axis to easily create full web applications.

You can see that this volume covers a lot of territory. This breadth may well be the book's largest flaw; its wide reach means no topic gets a really deep coverage and a number of topics do not get the coverage they deserve. Indeed I would have to say that only a much better Java programmer than I would get full value from this volume -- there were parts where the authors lost me entirely and it took an effort to get back my understanding, occasionally resorting to a Java manual.

The publishers have a page for the book that has an example chapter, table of contents, index and source code. The example chapter, 4, details how to build a SOAP server using Java and provides an excellent example for the book. If you're a little unsure of your Java skills, take a look at this chapter and see if you can easily understand the code and explanation. If you can, then this volume should have no surprises for you.

It should be said that nothing about the book's cover tells you how much of it relies on Java, though a good read of the table of contents makes it obvious. I would have personally preferred a book that was more general in the programming language it used, covering more of the tactics and methods rather than examining specific code. If, on the other hand, you are an experienced Java programmer looking for a book on programming web services in that language, then this is an excellent volume.

You can purchase Google, Amazon, and Beyond from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
This discussion has been archived. No new comments can be posted.

Google, Amazon, and Beyond More

Google, Amazon, and Beyond

Comments Filter:

  • web services (Score:4, Interesting)

    by Anonymouse Cownerd ( 754174 ) on Thursday March 11, 2004 @05:52PM (#8537375) Homepage
    both google and amazon offer their data as web services. that is, amazon has made available their database data in XML format. this allows you to do cool things like junglescan.com. google offers a similiar service, but im not too familiar with it. anyone care to elaborate?

  • I always shop at bookpool.com (Score:2, Informative)

    by Anonymous Coward
    www.bookpool.com [bookpool.com] is much cheaper. O'Reilly books are usually 40% cheaper.

  • Seems odd.. (Score:5, Funny)

    by Anonymous Coward on Thursday March 11, 2004 @06:01PM (#8537446)
    You can purchase Google, Amazon, and Beyond from bn.com

    Is it just me or is this odd?
  • I've been meaning to write this but never seem to find the time. Maybe someone already has, but I haven't been able to find this in open source.

    It seems to me it should be pretty easy to use Google's API to find the rank a given page has for a given query.

    It's easy to check the rank for a few queries, but I'd like to measure them for dozens, and several different pages too, so it would be very helpful to have it automated.

    Is there such a program?

  • How can Sun push web services? (Score:4, Informative)

    by Curt Cox ( 199406 ) <curtcox@@@gmail...com> on Thursday March 11, 2004 @06:34PM (#8537713)
    I'm a big fan of both Sun and Java, but it dismays me that they continue to push web services and try to make better tools and APIs for web services without making their sites accessible to web services. Why oh, why, can't they at least provide a nice web service for Bug Parade [sun.com].

  • Xen and opensource (Score:2, Interesting)

    by mhamel ( 314503 )
    Does anybody knows about Xen? It is a proposition for a programing language which use the document has a metaphor insteed of the object.

    Is has many advantages and makes more then some sence from a webservices perpective. I would love to work on an opensource implementation of something like that. It could be based on python (for example). That would do a great mix with zope.

    Anybody knows if something like that exists?
    • Can you elaborate more on object vs document? I've always thought of my documents as objects when I code.

      • Re:Xen and opensource (Score:2, Interesting)

        by mhamel ( 314503 )
        well here is a great paper about it: the article [cam.ac.uk]

        it basically says that when you use an API to access things like a DOM Node, you lose things like type checking and other advantages inherent to OO programming. They then go on and ask: "why not put that API in the language syntaxe?" The paper is great on the advantages of it has some very good examples.

  • Too simplistic? (Score:5, Interesting)

    by VP ( 32928 ) on Thursday March 11, 2004 @06:56PM (#8537889)
    Seems to me that this book is presented in a hobyist and simplistic manner. In the sample chapter we find this:
    sB.append("<?xml version='1.0' encoding='UTF-8'?>\n")
    .append("<SOAP-ENV:Envelope \n")
    ...
    .append(" <SOAP-ENV:Body>\n")
    .append(" <SOAP-ENV:Fault>\n")
    .append(" <SOAP-ENV:faultcode>")
    .append(42)
    .append("</SOAP-ENV:faultcode>\n")
    .append(" <SOAP-ENV:faultstring>internal error</SOAP-ENV:faultstring>\n")
    .append("<SOAP-ENV:detail>\n").append(ex.toString( ))
    .append("</SOAP-ENV:detail>\n")
    .append(" </SOAP-ENV:Fault>\n")
    .append(" </SOAP-ENV:Body>\n")
    .append("</SOAP-ENV:Envelope>\n");
    This is how building the SOAP fault is shown, and I don't think it is right. I thought there are plenty of tools in the Java world that will provide you with better ways to handle this - am I mistaken?

    • Re:Too simplistic? (Score:3, Informative)

      by Anonymous Coward
      Try Apache SOAP [apache.org]. Your sample would then be something like

      import java.util.Vector;
      import org.apache.soap.Fault;

      Vector theDetails = new Vector();
      Fault theFault = new Fault();

      theDetails.addElement (ex.toString());
      theFault.setFaultCode ("42");
      theFault.setFaultString ("internal error");
      theFault.setDetailEntries (theDetails);

    • Re:Too simplistic? (Score:1, Informative)

      by Anonymous Coward
      No, you're entirely right. The is building an XML document as a string, which is very easy to get wrong. In this case, consider if ex contained a single ampersand character, and how that would break it. It's very easy to build invalid XML when generating it this way.

      The only particular reason why you might want to build it as a string is if there are speed concerns, but you atleast need checks in place to ensure valid XML.

      And yes, there are SOAP generators for Java, which mostly allow you to do intellis

    • Isn't that why Axis is used? Personally, I find using Web Services with Axis to be simple. No more creating SOAP envelopes and such. It hides the details and lets you concentrate on the details.

  • Why a B&N link? (Score:1, Informative)

    by Anonymous Coward
    this book is $12 cheaper on amazon...

  • How long before Web Services finally dies? (Score:2, Interesting)

    by Anonymous Coward
    Web services were so big 1-2 years ago... and nothing. Absolutely nothing substantial.

    People are still clinging to this notion that Web Services is still the "Big Thing", but frankly it isn't. It's pretty mundane, and doesn't deserve the level of respect that it still seems to get.

    Remember all the hullabaloo over how Web Services will change the way the Web will work? How UDDI will allow different vendors to create competing Web Services and customers could choose between them? It would be the next gr

    • Re:How long before Web Services finally dies? (Score:4, Insightful)

      by Anml4ixoye ( 264762 ) on Thursday March 11, 2004 @10:22PM (#8539347) Homepage

      Well, yes and no.

      I think Web Services has its place. Is it going to "change the face of the web"? Perhaps, but not like the marketers say.

      Let's be realistic. Web Services, as you said, started getting big 2 years ago. Which means that is when most PHBs heard about it. And it represents a fundamental change in the way a lot of businesses function. Which means that it will take a significant amount of time to adopt.

      My personal feeling is that there are a lot of uses for it. Once we can get through the phase of competing standards, matching XML formats, etc, it is a useful tool.

      But to call it huge, I don't know. Does it have it's place? Absolutlely. We've used it to get disparate systems talking to one another, which, granted, could have been done with Corba, or anything else. But the learning curve is much faster for the Junior programmers.

      On the flip side, I think it is wrong to say it is going the way of the dodo. It has its use. Just like XML has its use. They *can* change the way businesses are run, but in the end, they will help in instances where they are needed, and save (or make) the companies money.

    • Well, This link probably won't paste in correctly, but Amazon shows 55,395,164 incoming links at http://www.marketleap.com/publinkpop/ [marketleap.com]

      I'd say the web services created a TON on incoming links to Amazon.
  • a site to provide exactly 2 web services:

    1. users register themselves with a uniquely assigned ID (1231513542352) and their current mailing address.

    2. other users look up the ID (1231513542352) to retrieve an unnamed address.

    now the first user just needs to tell businesses (more specifically, the businesses computers) where to find this web service and what their ID is. now the business computers can consume this web service and print out the correct mailing address.

    this is basically DNS for snail mail
  • last year's buzzwords, all strung together in one convenient sentence...

Slashdot Top Deals

Real Programmers think better when playing Adventure or Rogue.

Close