This book was a real disapointment. Like many programmers, I learn best by example. So I was hoping the code discussed in the book (and on the cd rom) would contain examples of working perl modules. However, it contains exactly three! And even those are so short, they hardly showcase the various aspects of coding a perl module. The rest of the scripts on the cdrom (the non-modules) are incredibly simple little jobs showcasing the abilities of >other< perl modules! Bummer.

This book is just a rehash of the POD (plain ol' documentation) provided with all the modules included on the CD. Thats about all that needs to be said. I'll elaborate however. As a professional perl programmer, it is my business to know what modules are out there, and thus I know many of them from CPAN. The last place I am going to look is in a big old printed book when I could do this instead: $ perl -MCPAN -e 'i /irc/' if i were looking, for, say, and IRC module (which the book of course doesnt cover). The copy of postgres included with the book is quite old and full of bugs. Newer versions are faster and more stable. There is a chapter provided on creating your own modules, but it is literally less than 2 pages long, and quite laughable on its face. If you want a book on Object Oriented Programming, get Damian Conway's _Object Oriented Programming with Perl_. It's far better. I gave this book 2 stars instead of one because the CD is useful if I am stuck somewhere on dialup and need a CPAN mirror (incomplete that it is).

I found this book to be very enlightening to expand the world of Perl modules to me. I was somewhat disappointed , however in the lack of detail in the GD graphics library area. The DBI documentation is right on and very useful.
Part of the beauty of the book is to describe processes you would have to wade thru many readmes. The GD Library part is deceptive as the GD library install has a lot of prerequitites, not listed in the book. The book shows some cool examples on the GD library ...a little more content in this area around the mysterious subject(maybe if they simplified this too) of how to create the shared library libgd. This appears to be a mystery on the web in general. I am not a novice PERL programmer and it was sad to see how convoluted it was to get the GD library to work vs, as described in the book. Bottom Line in this review....this is a book worth buying, however, be careful not to assume that getting thr GD module...one of the more glamourous modules discussed, is as easy as stated.
Doug and Frank...keep up the good work.your book helps to start fill a gap in the Perl module area....well written, easy to follow.

Part 1 (6 chapters) - Absolutely a waste of time, not worth a read. And the code examples are not related to JWSDP.

Part 2 (6 chapters) - Discusses on SOAP, UDDI and WSDL. The code discusses using a Older version of Apache SOAP and Apache Axis. The code needs a complete rewrite.

Part 3 - Discusses on JAXP, JAXB, JAXR, JAXM and JAXRPC. Good introductions but the JAXB chapter is based on DTD (which is obsoleted in the latest specs). JAXM and JAXRPC chapters just reproduces the Sun JWSDP tutorial...not much value addition.

Part 4 - Security, WSFL, WSIF (based on IBM Specs) currently these specs are obsolete no further releases.

It might've been a good book during 2002. The code and content needs an update to the latest specs and SOAP implementations.

Just as I stated in the title, it's a great book to start you with. It's written in a clear and precise manner where you could learn the basics of Java Web Services and not be intimidated by it.

It is a good introductory book to web services standards like SOAP, WSDL and UDDI but also goes further and talks about topics like WSFL, WSIF which are not covered by all books on web services but are essential to any real business processes exposed as web services where flow control and service unit(s) choreagraphy is as important as the single unit service request/response. Java specifications relating to web services are also covered like JAXM and JAX-RPC. I wish more examples and code was given, perhaps even a chapter or two, for ebXML which may not be a part of web services standards but still uses SOAP and defines industry standards for business to business collaborations especially dealing with supply chain commerce issues.
I agree with a previous reviewer (John Sfikas) that this book alone isn't exactly an eye opener for experianced professionals who have been dabbling with all the tools mentioned in this book like Apache SOAP, Axis, WSTK, Tomcat, Jetty etc. and know the challenges facing B2B collaborations on the internet quite intimately, but this book combined with "Building Web Services with Java: Making Sense of XML, SOAP, WSDL and UDDI" will give a much needed practical grounding to start making sophisticated web services in the real world. I highly recommend getting both these books but be prepared to use your brain and further what is presented in these books to deploy web services satisfying your needs. They will certainly not amount to spoon feeding you a near solution to your collaboration problems.

This book has a very unusual copyright notice. By using the information in this book, you implicitly enter into an agreement with Sun microsystems where any clean room Java implementations you write, from scratch, have to be submitted to Sun for conformance testing. I did not discover this until years after I bought the book. This kind of a "contract-by-fait-accompli" is illegal and unenforceable, but it may still be a pain to deal with. I suggest the Meyer and Downing book instead, since it is unencumbered.

the pace is a little stilted, and the plot is quite worn-out, but I love the wildly surrealistic sections...

If you're writing a Java compiler or Java Virtual Machine, this book is a must-have. It's also great for the serious Java programmer who is interested in the "guts" of how Java works. But if you want a tutorial on the JVM, you'll be better served by another book. Before you buy this book, you should also know that the on-line version is freely available.

This book is mostly inadequate for first time users trying to learn MicroStation. Explanations are too perfunctory, and in many cases lacking key information on how to make a specific command work; opting instead to tell you what the command does (if you are lucky enough to eventually figure out how to make it work). Considering the $60 price tag I had to spend for this book, it was a total waste of money.

First off this book is based on AutoCAD 14 and Microstation J. That information should be much more up front than it currently is. Since I am familiar with AutoCAD 2000 sometimes the book seems out of date. (well it is, acutally)

Secondly, Frank Conforti who writes the Microstation portions of the book, frequently says, "this is easy in Microstation." I get tired of not only the bias but also the oversimplification of the operations.

Thirdly, a great deal of the book covers the company histories of Autodesk and Bentley. The writers expressed the value of this to help understand the different philosophies behind the two packages. While I found it interesting, it didn't help me one whit to make me a better user of either program.

Fourth, the book deals primarily with the similarities of the two programs. While this is good for a beginner, it leaves unexplained the true power of each system because most tasks can be accomplished in several different ways. The book usually explains the way that is most similar in each program rather than the most efficient way to get something done in each program. The book doesn't cover the tremendous rendering capabilities of Microstation at all, since this is not something that AutoCAD does.

Since I think this is a book that would be most helpful to people who are just making the switch (not me who switched four months ago, 90% of what I would consider useful information I've learned on my own or from my fellow workers), it ought to have a chapter about first timers pitfalls.

One specific first-timer pitfall is the behaviour of the right mouse button. In AutoCAD the right mouse button is equivalent to hitting enter. It completes every command and restarts the command. In Microstation it is completely opposite; it behaves like AutoCAD's esc key. So the experienced AutoCAD user practically without thinking hits the right mouse button to complete a command, but he will discover to his dismay that nothing happens because he just cancelled the command. This just takes some getting used to.

Another thing that everyone tells the new user is there are keyin commands like AutoCAD's command line. Well, hardly. With AutoCAD to create a line all one had to do was type "l" and hit enter. To get microstation to do the same command from its key-in window, first you have to click with the mouse in the key-in window they type "place line" which can be abbreviated to "pl l". This is much more work than simply clicking the line tool from the toolbar.

It has two particularly useful chapters that each take a fairly simple project and go step-by-step through the process of creating the project using each CAD package.

It also has an excellent chapter on translating from one to the other. It points out the pitfalls and incompatibilities as well as explaining when you should and shouldn't translate.

If I've sounded critical its because I was really wanting a book that teaches more advanced features of Microstation. This isn't it.

If you want a nice history of computer aided design, this is a good book. Or if it is your first time using Mircostation this would be pretty handy (though it needs the chapter I described above)

As a beginner to Microstation I had a time with the first example. I'll admit I am biased towards Autocad as that is what I've used for ten years.

I was hoping for a book that shows how to do each Autocad command in Microstation. This book does not do this very completely. The index of the book does not list all of the command sets of either program, so you are not getting a lot of coverage on most topics. Trying to find answers to everyday problems is not possible for the most part with this book.

My suggestion to anyone who truly wants to learn the other program whether it be Microstation or AutoCad is get a good book on either subject. The most accomplished Microstation user I know swears by Frank Conforti's books on Microstation.

This is one of the worse books I have read in the analytic literature over the last 20 years. Please, read Greenberg & Mitchell, and skip this god awful text! Summers says nothing new, and his uninspired prose is sure to bore.

Dr. Summers bring to life a wonderfully comprehensive, detailed and intelligent text on object-relations. Although each chapter stands on its own merit, Dr. Summers is able to compare and integrate various theoretical perspectives at a very precise and deep level. He articulates clearly the subtle differences between various theoretical points of view, thus providing a useful text for the beginning and seasoned therapist alike. His chapter on Winnicott's thinking, for example, is one of the clearest disuccsions of this analyst that I have read. I recommend this book highly. Dr. Peter Shabad

This book is an invaluable introduction to or review of the works of the most important object relations theorists, including Fairbairn, Guntrip, Klein, Winnicott, Kohut, etc. Although it covers ground similar to that summarized in other works, including the until-now standard text by Greenberg & Mitchell, it is far superior in a variety of ways to the latter. It combines accesibility with accuracy and insight, and includes not only interpretive overviews, but a great deal of contextual material, including information on the influence of each writer under discussion and, most usefully, case material that elucidates the theoretical concepts discussed.

Because of the clarity of the writing and the organic intertwining of theory and case discussion, this book is irreplaceable as a teaching text, appropriate for graduate students, psychoanalytic candidates, and even perhaps some advanced undergraduates studying psychotherapy theory and practice. I have used this book in my work teaching graduate clinical psychology students for several years, and the students are unanimous in their enthusiasm. Both they and I have clearly benefitted from Dr. Summers' insights.

I was quite disappointed with this book. Although it does provide some interesting insights into how Japan let itself be drawn into a disastrous war with China and the West, too much of the book reads like an anti-military, anti-Western polemic. For example, while there is plenty of material on Japanese atrocities against Asians (and it must have taken courage for Ienaga to present this material to his countrymen) there is virtually no discussion of Japanese atrocities against Westerners. Ienaga is also curiously restrained towards Russia; he argues that the Kwangtung Army provoked the Russian attack into Manchuria in August 1945, which is absurd, and manages to blame the Americans for the Russian seizure of the Kuriles. His description of American misbehavior in Japan after the war is grossly exaggerated; although he discusses the shameful behavior of the Japanese postwar government in setting up a system of prostitution to cater to American occupation troops, he fails to mention that this organization was dissolved on orders from McArthur. Writing in 1968, during the height of the Vietnam War, Ienaga condemns the United States as the new agressor in Asia, suggesting a moral equivalence between the Japanese military of the 1930s and 1940s and the American military of the 1960s that I found awfully hard to swallow. Ienaga's political agenda definitely gets in the way of his telling of history.

For those who are ready to read a book from the Japanese viewpoint owning up to their atrocities during World War II, this is NOT the book. Nanking is addressed in less than 2 pages with the only citation of Chinese dead at 20,000. Not one word is written about the Bataan death march and the horrendous treatment of Allied POWs by the Japanese in Japan and areas throughout Asia and the Pacific.
I found Ienaga's explanation of Pearl Harbor lacking. He explains, "Yet the American government gained an even greater psychological advantage. By allowing Japan to strike the first blow, even the isolationists were swept up in the patriot clamor for war and victory." (pg. 137) By allowing?? Is he referring to the U.S. option of mounting its own secret first strike?
Ienaga states, "The Auschwitz gas chambers of our 'ally' and the atomic bombing of Hiroshima and Nagasaki by our enemy America are classic examples of rational atrocities." (pg. 187) I'm am sorry, but to relate the holocaust to the bombings of Hiroshima and Nagasaki is beyond belief. Make no mistake about his accusation as he later states, "Nevertheless, Pal was correct in stating that the decision to use the atomic bombs on Hiroshima and Nagasaki closely resembled the orders issued by German leaders brought to trial as war criminals at Nuremberg." (pg. 201) He then continues with, "The harsh treatment of civilians in Manchuria had its counterpart in Japan under U.S. occupation forces." He continues, "The violence came later, however, in the assaults, robberies and general mayhem committed by American troops against civilians." (both pg. 236) Now U.S. troops in Japan are equivalent to Japanese troops in Manchuria!! Does he ever stop?
There may be some redeeming sections to this book, but it is not worth the insult to anyone's intelligence to wade through the waste. My suggestion is to bypass this book and spend your money on another book for a look at the Japanese in World War II.

Americans may be startled to pick up a 256-page book about the Pacific War and discover that Pearl Harbor isn't mentioned until page 135. That's a consequence of Ienaga's belief that the war actually began with the Japanese army's 1931 coup in Manchuria, which led inevitably to war with China, which in turn led to the wider war agaisnt the western Allies. Despite Japan's claims about liberating Asians from colonialism, its purpose in going to war was to obtain the raw materials with which to defeat China. That was one reason the Japanese treated the "liberated" peoples so badly--as badly as they treated their white PWs.

Part of the blame goes to the Japanese military tradition, in which the officers were an elite and the troops were conscripted from the younger sons of tenant farmers. Brutality was the norm, and the enlisted men who stayed in the army and became sergeants were precisely those who would most brutalize the next batch of recruits. Draftees were called issen gorin--roughly, "penny postcards," because that was the cost and the method of obtaining one. Why husband the life of a soldier when he could be replaced for a penny? Ienaga explains that the enlisted soldiers were the bottom of the food chain, that they had no on upon whom to vent their brutality in return.

During WWII, it was fashionable in the U.S. to show General Tojo as the Japanese dictator, making a trio with Germany's Hitler and Italy's Mussolini. But of course that was very far from true, as even American propaganda recognized, since sometimes the emperor Hirohito filled the same role. Ienaga is especially good at explaining this mystery, in which a dictator was imposed by a group of elder statesmen--then deposed when his usefulness was over. Tojo ruled the government and the army, but he never managed to rule the navy--he didn't even learn about the defeat at Midway until a month after four aircraft carriers and a major portion of the navy's fighter planes had gone to the bottom.

This is a valuable book, one of only a half-dozen serious studies by Japanese scholars of World War II available in English. We didn't know our enemy in 1941; we hardly know him any better today.

This review concerns the revised 1966 edition. Frank and Joe investigate the theft of a number of stuffed animals from a country auction and aid their father with his case concerning an industrial spy ring that is using short-wave radio to send coded messages containing the names of various wild animals. This book was average; the mystery was alright and it had a moderate amount of action. Most fans would probably not be bored with this book, but I don't think that many would be very excited by it either.

This review concerns the original 1945 edition. Frank and Joe help their father capture a group of thieves that steal valuable radio equipment and communicate in code using short-wave radio. Also, an old friend of Mr. Hardys asks for the detective's help in locating some missing friends. This was the first book in which Chet had a hobby (in this case, taxidermy) that played a part in the mystery. Not much to say about this book, actually, it's neither good nor bad, just average. The mystery is not spectacular and it's not boring either. Most Hardy Boys fans would probably not be very excited by this book, but it probably won't put them to sleep either.

McFarlane wrote the original version of the book during his second stint with the Syndicate. I think the Syndacate had other ideas and let McFarlane finish The Melted Coins and World War II end before letting the hammer fall. In 1945 when the war ended this book was published then the heat was put on the author to bring the Hardy's into the scientific age. Like any of us at work, when change is implemented, we react with negativity. McFarlane at this point I feel became uninterested in the series and wrote his worst book to date only to be surpassed in 1947 by The Phantom Freighter. The book was average by the sets standards but sub par by McFarlane's standards. The revision was not much worse. Taxidermy become the sub plot and fingerprinting is performed for the first time in the series in this volume. The child like innocence held in the earlier volumes is now gone.

ORIGINAL Rated C+ Revision: Rated C

My last critique of this book looks harsh to me now. While it is true that this isn't a who done it, it does raise awareness. The only words I still agree with from my last review after a year of contemplation is.....The (only-NOT ONLY) good thing I find about this book is that it does get Anna Mae's name out and about and on people's minds. The book is not a who done it. -- The writing style no longer seems to be so crystal mystic'y', it has a flow of its own. I recommend this book as a source of background information regarding some of the details surrounding the life of Annie Mae. Jennifer

This book begins with a five page list of AIM casualites that occured on Pine Ridge Reservation between the years of 1973-1976. As the author points out, these are "documented homicides"-the actual number could be as high as 300 or more. One of the documented homicides is Annie Mae Pictou, a 30 year old AIM leader and mother of 2 small daughters. Claypoole's book is a passionate investigation of her life in the various genres of poetry, journalistic writing, and interviews of people who knew Annie Mae, but are reluctant (to this day) to speak any truth regarding her life, and death...she was found in a ravine on the edge of Pine Ridge Res, February 24, 1975 with a bullet wound in the base of her skull. As part of the autopsy, her hands were severed at the wrist and sent to Washington, D.C...she was then buried as "Jane Doe", cause of death listed as "exposure".Urged by Canadian family members, the body was later exhumed, revealing the execution-style death, and identified as Anna Mae Pictou...in the words of Anna Mae Pictou: "I am a part of this creation as you are, no more and no less than each of you within the sound of my voice. I have a right to continue my cycle in this Universe undisturbed." This book speaks for Anna Mae Pictou's fierce desire to exist with the dignity of a free human being among other free human beings. THIS BOOK IS HER HANDS.

This book is filled with passion and insight; they ooze from thepages....Knowing the author and knowing the book, I can state that there is honesty in each line. Integrity in each concept. Read the book. Experience the heart.

The book presents information about various performance measurement tools, but lacks the depth to explain things in detail. The author mostly presents what the man pages describes, but does not go into any detail as to what to look for or how to go about tuning the system, all is left up to the reader to figure it out.

The book is probably good for a beginner, but not for the seasoned professional who requires a more detailed approach to Solaris capacity planning and performance measurements.

If you really want a good book on performance and tuning, I suggest one to look elsewhere; books such as System Performance Tuning (by O'Reilly & Associates), and Sun Performance and Tuning (by Adrian Cockcroft) will meet the the serious Sys Admin needs.

Does anyone edit anymore? Typos abound and even appear in examples of parameter setting. I realize there is value in "speed to market", but in this day and age, simple proofreading should be mandatory.

This book provides a good introduction to the topics as related to the Solaris operating system. It also includes information about topics not addressed in the regular Sun documentation, such as new daemons for DNS caching. Highly recommended.

Possibly the worst book I have ever read. Certainly one of the top 10 worst books I have ever read. The author fell over himself to fill the pages with words. The characters were unbelievable and the story line ridiculous. Do not waste your time.

I think this is one of the better police thrilers of the time period. He defiantly has a good one here also. He just produces wonderful character driven stories that when they work (and this one does), they really grab you. The tension is there though out the full book. The story is very developed so much so that you see the crime sceens. Another thing about his books is that they do not play to the lowest common denominator for action books; he gives the reader some respect and expects an IQ over 70. A good book that is worth the time.

I don't normally read police procedurals but this one is an exception. "Wallflower" is by far the best of the Janek novels. It also has the least amount of sex in it of the three. If Bayer had left the better part of the sex to the reader's imagination in all three novels he would have done even better. This is a great read, especially for those who would profer to avoid Ed McBain and/or Joseph Wambaugh but would still like some balance in their mystery reading. If you enjoy the Janek novels as I have you will also enjoy the seven movies based on these books.