There is hardly any significant fact about viruses that missed-out in this edition of "Fields Virology". Page after page, this sound all-inclusive reference doles out authoritative information on both viruses and viral syndromes. From taxonomy to etiology, metamorphosis to replication; the analyses of this text is grand. The same applies to its attached CD-ROM. Its practical outlook was intended to benefit both microbiologists and pathologists. Bernard Fields and his colleagues made their mark with this book. It is a great effort.
However, most botanist may not be pleased to know that little attention was paid to plant viruses. Again, many potential buyers may be demoralized by the rather high price that this virology-set demands.

It covers all fields of virology. Perfect and wonderful ! Easy to understand. I really recommend this book to who is involved in biology

I bought this collection for one reason and one reason only: it contained another slice of Ian McDonald's world-turned-upside-down 'Chaga; sequence. As it turned out this was by far the best piece in the book, but more of that later.

I haver never been convinced by Pater Hamilton, much as I want to like a British author who can do cyberpunk and do space opera with the best of the yanks. However his piece in this collection, 'Watching Trees Grow' changed my opinion of him. It is an alternative-history crime novella based on the premise that descendants of the Romans still rule Britian through a set of East India Company-style families who combine economic control with a monopolies over various areas of scientific progress. It is a neat idea, and takes the premise further than many other alternative histories by throwing the story further and further into the future, as an old rivalry becomes an obsession that almost transcends time.

I enjoyed it despite the episodic feel - perhaps a novel would have been more appropriate - but its 'Britishness' seemed slightly musty and old-fashionned, and redolent of dreams of Empire, in stark contrast to McDonald, or more overtly hip authors like Jeff Noon or Justina Robson. Maybe that was the point, and if so it was well made: science fiction is much the poorer if it doesn't teach you something about the society in which you live.

As for Stephen Baxter's 'Reality Dust': well, he does try, and he does keep churning them out, but this is so boring and so mainstream and so traditional. It is all done very competantly, but it is basically the kind of SF I enjoyed when I was a teenager, it isn't challenging in any way.

I was a little disappointed with Paul McAuley's novella, 'Making History', especially as he is one of my favourite writers. This was partly because at the heart of it was a very tedious old argument about the nature of history (great men versus social processes) which tended to intrude on the quite interesting story of the processs of war, defeat, reconciliation and the way history is written. Perhaps this was set up as part of the character of the historian to demonstrate his own flaws, but it didn't really convince. This is certainly not one of his best stories.

As I said at the start, I bought this collection for Ian McDonald's 'Tendeleo's Story'. I was certainly not disappointed by this one. McDonald is one of the few writers in the genre today who can combine real politics and a strongly compassionate and empathetic grasp of human nature. He is also a superb writer, able to portray setting and character in a vivid, dynamic and sensual way.

This novella, as the title suggests is the story of Kenyan girl, Tendeleo, the arrival of a extraterrestrial nanotech lifeform, the Chaga, that begins to transform Africa, and as a result the balance of global power. Initally for Tendeleo, however, this means growing up and simply trying to survive in the ferment that follows, which in her case means geting more and more deeply involved in street gangs smuggling Chaga material out of Africa. Capture and exile is never far away and whe it comes she loses here family in tragic and guilt-inducing circumstances. She winds up in cold, rainy Manchester, England, where she meets the other central character and narrative voice of the story, Sean, a black Irishman, who is also an exile in various ways, and a tentative love affair begins. Of course, inevitably Tendeleo has to return to Africa, where the Chaga has begun to revolutionise everyday life and the place of Africa in the world.

'Tendeleo's Story' is worth the price of this collection alone. It is an almost perfect example of how to write a novella that with none of the structural problems of the others in the book. The narrative is perfectly paced, with a deft handling of both action and emotion and no forced-ness or pretension. It is truly worthwhile and heartbreakingly real story that exist within an utterly fantastic and transforming world, yet a world which says so much about our own. A true gem of a story, from one of the best and most underrated writers around.

This volume is somewhat different than the usual flurry of anthologies that come out, especially during the holiday season, on two counts.

First, it is a British import, and thus the authors represented, while to varying degrees familiar to most of the rest of the world, really are British in tone and outlook.

Second, rather than stories, this volume has the longer novella form for the stories, and thus there is one story apiece. SF seems to be the last bastion of this "not quite short story, not quite novel" length work, and the virtues of the form are admirably displayed here.

The first story is Peter F. Hamilton's WATCHING TREES GROW. Although far better known for his Reality Dysfunction space opera, Hamilton has written detective SF before (The Mindstar Rising novels) and this is another example, with a twist...it is set in an alternate history where Heinleinian long-lived families vie for power and influence, and that is just the backdrop to a murder mystery.

The second story is REALITY DUST by Stephen Baxter. Unlike Hamilton, Baxter's story is set in his trademark universe, the "Xeelee Sequence". This is set after the Qax Domination, where their former collaborator-lackeys seek escape from the freed peoples of Earth in a rather unusual escape route.

MAKING HISTORY, by Paul McAuley is set in a more standard "near future" solar system, in the aftermath of a war...and even if it is true that history is written by the victors, that history can sometimes be rather muddled in the making.

The last story is TENDELEO'S STORY by Ian MacDonald. Like the Baxter, it is set in a trademark world of his, the "Chaga stories", where a strange alien life (nanotech? technolife?) has started to colonize the Earth, beginning with Africa. This story, like his other novels and stories, focuses more on the people affected by the Chaga, much more so than the actual event itself.

All four of these stories are strong, but of course, tastes may vary. The stories do range a far chunk of SF, and it is very possible that while you might like two or three, you may not like all four (personally, I liked the Baxter the best and the McDonald the least). Thus, the 4 star rating. Still, all in all, if you are at all interested in what the best British SF writers are doing, this paperback is perfect for the purpose.

Four novellas that are everything that is great about science fiction. These four authors are absolutely among the greatest voices in the genre today.

In WATCHING TREES GROW Peter Hamilton took history, turned it upside down, shook it a bit & gave us an alternate view of a history quite unlike anything I had ever read before.

Stephen Baxter's REALITY DUST made the reader look at reality in a whole new way.

In MAKING HISTORY, Paul McAuley showed how history is not always written by the victor.

Ian MacDonald's TENDELEO'S STORY took me back to the Chaga in EVOLUTION'S SHORE which always impressed me as being one of the most possibly real First Contact stories ever written.

All four novellas explore the very trait of our species' survival, adaptability, that brings hope & after all that's what science fiction is really about.

A story that is not very plausible. A writing that is shallow and one-dimensional. There certainly are better mystery stories around.

I thoroughly enjoyed this book. This was the first Peter Lovesey book that I read and I think it has to be one of his best.

"Rough Cider" is by far the best work of British author Peter Lovesey. It has beleivable characters and a plot that will keep you up until you've finished it.

What a book..."The Book of life." Why it's a modern cartoon book of paleontology. Though its wonderful life-like illustrations and tree-of-life charts are delivered as scientific facts, they are simply graphic theories that illustrators doll up into hypothetical reality. If you like science and fiction, here is a book for you. The realistic pictures belie the text, which says: "We do not even know how to conceptualize, much less to draw the worldview that would place Homo sapiens into proper relationship with the history of life."

Its authors caveat is that "science can only operate as a work in progress without perfect knowledge, and we much therefore leave a great deal out from ignorance --- especially in a historical field like paleontology, where we must work with the strictly limited evidence of a very imperfect fossil record." It's that fossil record, that the book presumes is accurate in its layer-by-layer record through time, that requires scrutiny. The oldest fossils are found in the bottom layers and the youngest in the top layers of rock, but little or no evidence is presented to provide skeptical readers information they can decipher for themselves as to the accuracy of fossil dating by rock layers. Are we to believe, without exception, that the fossil record is progressive from bottom to top? What about fossilized trees that protrude through millions of years of time? They are conveniently omitted. Michael Benton of England's Bristol University, one of the book's contributors, says "All the periods in the geological time scale receive their names in recognition of obvious changes in the fossil record." Yet, to the contrary, Benton adds, "the history of Earth's crust has been far too violent to preserve much more than a random sample."

Its general editor, Stephen Jay Gould, is magnanimous in his promotion of a single theory of man's origins, from monkeys he and most other fossil hunters say.

There may be missing pieces to the paleontological puzzle, but the bone diggers cliam they have finally filled in the evolutional blanks and can conclusively attest to the idea that life evolved from simpler single-celled organisms into modern man. The book's most ardent opponents are taken head on by Gould: "The lack of fossil intermediates had often been cited by creationists as a supposedly prime example for their contention that intermediate forms not only haven't been found in the fossil record but can even be conceived." But Gould holds a trump card. He says: "a lovely series of intermediary steps have now been found in rocks.... in Pakistan. This elegant series, giving lie to the creationist claims, includes the almost perfectly intermediate Ambulocetus (literally, the walking whale), a form with substantial rear legs to complement the front legs already known from many fossil whales, and clearly well adapted both for swimming and for adequate, if limited, movement on land." Oddly, the book never shows a drawing of Ambulocetus, but does have an illustration of a skeleton of a 400-million year old fish with a small underside fin bone the authors claim "must have evolved" into legs in four-legged animals. Man's imagination is not found wanting here. Out of millions of fossils collected and stored in museums, is Ambulocetus the main piece of evidence for evolutionary theory?

Richard Benton says that Charles Darwin had hoped the fossil record would eventually confirm his theory of evolution, but "this has not happened," says Benton. Darwin hoped newly-discovered fossils would connect the dots into a clear evolutionary pattern. The book attempts to do that with its fictional drawings of apes evolving into pre-humans (hominids) and then modern man. Yet the book is not without contradictions. It says: "It remains uncertain whether chimpanzees are more closely related to modern humans or to the gorilla."

The horse is shown as evolving from a small, four-toed to a large one-toed animal over millions of years. There are different varieties of horses, yet there is no evidence that a horse ever evolved from another lower form of animal, nor that horses evolved into any other form of animal.

Another evolutionary puzzle that goes unexplained in the book is the pollination of flowers. How did bees and flowers arrive simultaneously in nature? What directed the appearance of one separate kingdom of life (insects) with that of another?

The book describes 6 1/2-foot millipedes and dragonflies with the wing span of a seagull, but gives no explanation for them. Life was unusual in the past and not all forms fit evolutionary patterns. Consider the popular supposition that life evolved from the sea onto land. That would make more advanced forms of intelligence land bearing. But the aquatic dolphins defy that model, since they are among the smartest mammals.

The book maintains an "out of Africa" scenario for the geographical origins of man, but recent fossil finds in Australia challenge that theory and even the book's authors admit that "a single new skull in an unexpected time or place could still rewrite the primate story." Consider Java man (Homo erectus), once considered the "missing link" and dated at 1.8 million years old. Modern dating methods now estimate Java man to be no more than 50,000 years of age, a fact that was omitted from this text.

Creativity, invention and language are brought out as unique human characteristics. Yet the true uniqueness of man is not emphasized. Humans biologically stand apart from animals in so many ways. Humans can be tickled whereas animals cannot. Humans shed emotional tears, animals do not. The book does not dare venture beyond structure and function, beyond cells and DNA, to ask the question posed by philosophers --- does man have a soul? The Bible speaks of a soul 533 times, this "book of life," not once.

Gould's temple is science. He calls the scientific method "that infallible guide to empirical truth." Science works by elimination. It can only work from experiment to experiment, eliminating what is not true. It can say what is probable, it can never say what is true. Gould appears to begrudge the shackles of science by stepping outside its boundaries in overstating what it can accomplish. Whereas creationists await the day they will stand in judgment before God, for the evolutionists Gould says "Someday, perhaps, we shall me our ancestors face to face." Imagine, standing there looking at a man-like monkey skeleton.

One cannot fault the flaws in this book. After all, it was written by highly evolved apes.

You would have expected more time and detail to the ermergence of the nervous system and the Cambrian Explosion. A more up-to-date section on human evolution (no mention of Ardipithecus Ramidus) but on the whole the book is a good synthesis of the state of the knowledge in this field.

This singular book gives a very nice popular overview of the state-of-the-art in paleontology, chronologically covering everything from the Archean to the evolution of man. It is a beautifully illustrated and well-written book, although the text is perhaps sometimes a bit too technical and dense for the paleontological novice.
And please don't buy some creationists' claims that this is science fiction. The contents of this book is based on material from thousands of scientific articles in peer-reviewed scientific journals such as "Nature" and "Science", representing the fruits of the hard labour of paleontologists from all over the world. And the fossil record, even if it is convincing in itself, is far from the only support for evolution. Independent evidence for evolution can also be found in biogeography, development, molecular analyses (gene DNA, junk DNA, mtDNA etc), anatomical analyses, and even field observations of new species evolving. This large amount of evidence is why evolution is considered an established and undisputable fact. Of course, if one rather than facts wants comic book fantasies such as humans coexisting with dinosaurs and evil scientists conspiring to hide the truth, then one should look for creationist books instead. Or comic books.

Moving from the IIS environment to the Unix environment; being fairly computer literate and having become quite familiar with basic Unix administration, I was looking for a good source to get me up to speed on Apache.

This book is not it.

It assumes a fairly detailed basic knowledge which most 'newbies' to the Unix/Apache world just do not have. After I had learnt quite a bit about Apache (from another source) I found this book excelent to tune that knowledge. It is however, as the title 'Professional Apache' suggests, for the Professional Apache administrator. Don't get it to learn about Apache, get it when you already know quite a bit about Apache, and need to learn how to refine that knowledge and need to tweak Apache for maximum performance!

Wainwright is incredibly knowledable, but like many knowledgeable people he forgets that for the average Joe to get from A to Z he has to go via BCDE & F and can't start at UVWX & Y. This is not a criticism of Peter but rather is a criticism of the Wrox editorial staff.

I do feel that the editorial staff could, with a little intelligent effort, have helped Peter create a book that could indeed have become the 'bible' of Apache Administration.

Peter Wainwright has done another fine job of covering the installation, configuration and running of Apache, this
time focussing on version 2.0 of the application.

Much of the material in this book was covered in his previous edition (Professional Apache), though the obvious
emphasis here is on Apache 2.0. However, Apache 1.3 isn't ignored and the book is still useful for anyone using
that version, as well as anyone simply migrating to 2.0.

As before, it starts with a basic overview of the HTTP protocol, TCP/IP and server hardware. These are useful for
beginners, but I'd hope that anyone thinking of running a web server would have this knowledge already.

The section on improving web server security has been expanded into its own chapter and includes plenty of useful
system security and integrity advice not peculiar to web servers, but crucial nonetheless. The chapter on
extending Apache with third-party modules has had an overhaul too, now covering the likes of WebDAV and
mod_python. mod_perl, which has changed drastically for Apache 2.0, is also covered in detail for both versions of
Apache.

I've recently built an Apache 2.0 server from scratch using nothing but this book, and apart from a couple of
typos I've found it to have covered every step of the way without coming across any errors or omissions (the index
is very good but in the May 2002 print I have some of the entries are one page out). The book is still very
Unix-centric, though there seems to be more specific information for Windows users than in the previous edition.
But then who would run Apache on Windows anyway? The author makes his views clear near the start of the book that
Unix is a preferable platform, but for the masochists there seems to be enough information to get Apache running
on Windows.

If I have any complaints it's that perhaps the chapter on monitoring Apache could have been expanded somewhat in
its description of log analysis tools. Only Analog is covered in any depth, though it is described in plenty of
detail from installation to configuration and is arguably the most useful analyser out there anyway.

Professional Apache 2.0 isn't a bed-time read, but it's an excellent tutorial and reference for the Apache
administrator and far more useful than the online documentation. If you are planning to install or run Apache,
then I highly recommend this book.

Apache's HTTP server has been by many measures the most popular web server on the web, and perhaps the primary application that drives people to Linux and open source. Three years ago, Wrox published the definitive book on running the Apache server by Peter Wainwright. Excellent though the book was, it badly needed updating. In May 2002, Wrox published another book, Professional Apache 2.0, which covers the new generation of Apache server, as well as older 1.3x versions that are still running production servers around the world."

Although Apache changed a great deal in its version 2.0, it is a credit to the Apache folk that the config files and command line options have basically remained the same for sys admins. For this reason, the book seems to include a lot of material (CGI security, building, core modules) from the original book. However, a closer look reveals many changes. Almost every chapter includes a discussion about how features differ in both versions of Apache. The book does a good job of giving an overview of Apache's architectural changes and how the use of multi-processing modules (MPM) allow the admin to choose an optimal implementation of apache. This edition, noticeably bigger than the previous one, contains many more examples of how one can extend apache functionality (configuring for binary distribution, setting up virtual interfaces, load sharing). Many sections have been expanded. The discussion of security and SSL is more detailed, yet more succinct; so is the section on content negotiation, (which is twice as long as the previous book), doing proxy server configurations, rsync and benchmarking performance. The discussion on hardening the server was great and up-to-date, although I wish the book spent more time discussing on patching and upgrading.

What is new to the book? We find a longer discussion of graphic administration tools for Windows and Unix, including webmin (which actually I wanted more of). We also have discussions of newer modules such as mod_ruby, mod_python, mod_dav as well as a brief description on how to install tomcat alongside apache. The discussion of mod_dav was especially helpful and interesting to me (and I was especially glad that the author acknowledged the Subversion DAV module, something which is bound to become more important). The php stuff hasn't changed much (although at the time the book was published, 2.0 compatibility with PHP was still an iffy proposition). The book's discussion of mod_perl isn't significantly different, although it does point out migration issues and some additional features.

Generally, the book is clearly written and contains enough examples to find any configuration you want. A few parts required rereading (especially the part about proxies and proxypasses), and occasionally I needed a better explanation of what the example code was supposed to do.

No book can be everything for everybody, and nobody can accuse the book of not having enough content (it is after all more than 700 pages!). I found myself wishing for other things. The book briefly discussed 2.0's support for ipv6, but I longed for a fuller explanation and a more detailed example (Fortunately, I had seen a good ipv6 tutorial on Linux Journal ). Also, I would have liked more information about other web application servers (like zope that Apache sometimes coexists with, content frameworks (such as cocoon) and other goodies produced by the Apache Foundation. The author might legitimately feel that such subjects lie outside the book's scope, but such topics are becoming more important.

In summary: for newbies who are looking for a guide to start with: this is the definitive book to read. It's definitive and a little imposing, but it is well written and logically arranged.

For people already familiar with Apache 1.3 but looking for more depth about ipv6, php, content frameworks or Tomcat, it might be better to read books on those specific subjects instead of this one. Indeed, Wrox will soon be coming out with a book specifically on Apache and Tomcat.

For experienced system administrators, the material in this book may not be terribly new, but they will still appreciate the variety of configuration examples for managing large numbers of virtual hosts and the convenience of having documentation of the 1.3/2.0 differences at their fingertips.

Stephen Jones, lead counsel for Timothy McVeigh, writes an interesting account that hypothesizes that his client and Terry Nichols were not alone in planning and carrying out the Oklahoma City bombing. Jones not only presents many deficiencies in the Federal government's case against McVeigh in the Oklahoma City bombing, but also paints the picture of a government agency completely hell-bent on "winning" its own case. Jones, in advocating for his client, contends that the prosecution's case was incomplete and circumstantial; exculpatory evidence was either withheld or stalled that could have helped in giving McVeigh a fair trial.

In his analysis, Jones does raise some doubt in McVeigh's "direct" involvement in the bombing, and more that one can of worms is opened (Cannot mention here because that would kill interest in the book). Several red flags imply that the bombing was planned from abroad. That is to say, how can only two men plan and execute such a bombing of such magnitude, something said to be impossible by bomb experts in other countries where this kind of thing is routine? Jones questions Terry Nichols' ignorance of the OKC bombing plans. Nichols made several trips and many telephone calls to the Philippines, a hotbed of terrorist activity -- that's never taken seriously in connecting Nichols, much less in mitigating McVeigh.

Jones' book is also his own biographical foray into a high profile case that transformed his life and his beliefs about U.S. justice. His book is not intended to cash in on this case, but to expose some theories that had not sufficiently been discussed. Jones believes McVeigh should have been found not guilty (Read the acknowledgements! Although Jones does not offer a satisfactory explanation as to why McVeigh was involved at all, this would seem to be covered by attorney-client privilege. Despite this, whether or not Jones convinces the general public of the facts that McVeigh did not receive a fair trial and that the government successfully hid the truth is left for the reader. At the very least some interesting theories grounded in fact are presented. A limitation is that there is only one illustration within the book; however, an overall good book.

This book is not really about whether Tim McVeigh was or wasn't guilty in the Oklahoma City bombing on April 19th, 1995. This is not a "true confessions" sleaze piece told by a self-aggrandizing "ambulance chaser" lawyer. All of that is really moot now that McVeigh has been executed.

What this book is about is the fact that Tim McVeigh and Terry Nichols could not have pulled off a bombing of this scale off by themselves (not because the author says so but because unimpeachable terrorism experts say so). It is about a government that seems blind to evidence pointing to a much broader conspiracy; possibly even foreign backed. It is also about the lengths to which your government will go to get its way. Truth and justice have NOTHING to do with what went on in United States vs McVeigh and this should concern every American deeply.

The author, McVeigh's appointed defense council, takes it from the beginning and walks the reader through the entire sordid process of trying to conduct a fair, Constitutionally guaranteed trail against the U.S. Justice Department who basically are in control of the whole process. This is like putting the fox in charge of the hen house.

He explains how the prosecution made every effort to unfairly deny and or delay the defense's access to vital FBI evidence (remember the 3000 pages of documents that the prosecution "misplaced" that came out recently?) He tells how the prosecution lied and tampered with evidence. He tells how the FBI refused to let the defense examine the crime scene in detail and then demolished it before the trail began forever burying its secrets. He explains how the government manipulated and changed their stories to fit their version of the crime without any real evidence. He explains how the judge appointed by the government to preside over this case refused to let the defense bring witnesses and introduce evidence that would most certainly have brought reasonable doubt to a fair-minded jury. He explains how the same judge changed much of the way the Nichols case was handled which resulted in a verdict of life without parole instead of death and much more.

In short he lays out the blueprint for a government run lynching that spits in the face of everything we have been brought up to believe our justice system is about. This book will disgust anyone with the least bit of fairness and decency and it will tarnish forever any remaining belief that our government is above reproach.

Now, one might say that this is just "sour grapes" on the author's part because he lost. I suppose it could be but that's not the way the book is written and it is not the way the author comes through. He does not engage in any sort of bitterness one would associate with a "sore loser". In fact, he goes out of his way to congratulate and acknowledge many of his detractors and opponents despite their attacks on him before, during and after the trail. In every way the author comes across as a fair and decent man who is only interested in the truth. Read this book and also read "The Oklahoma City Bombing and the Politics of Terror". There is more to this than we are being told.

Forget or ignore the fact that Jones was McVeigh's lawyer. This book is an excellent historical account of the event, and a great accessory to another interesting take on the bombing, the book "The Secret Lives of Bill Clinton," and articles on thenewamerican.com. Unavoidable facts detailed clearly in this book include the extra human leg found in the ruins (combat boot and sheath intact -- all 168 dead had both legs recovered), numerous eyewitness accounts/testimony denoucing nearly every point of the Justice Dept.'s ludicrous "lone-bomber" theory, and the cirus McVeigh and cohorts launched in the months before the bombing which exposes McVeigh for what he is -- a willing 'Patsy' who could never have pulled this off alone.

If you don't want to be up at nights thinking about the case, then read American Terrorist -- the McVeigh-sanctioned lie-a-thon that gives him the twisted glory for the attack, and the book that will let you sleep at night knowing the only person you believe responsible is behind bars.

If you want the truth, read this book. You'll realize that McVeigh is laughing at the latest FBI fumble with the recently turned over 3,000+ pages, he is pleased with the new FBI embarrassment and will probably ask for a new trial just to make the gov't look even worse (even though he'll still be convicted), and that the recent release of the documents was probably delayed by the sophomoric Clinton-Reno administration in order to pass the blame onto Mr. Bush.

Regardless of your beliefs about the bombing, you won't be albe to ignore the facts about the extra leg found, and the facts about ANFO bombs and their inability to be driven 300 miles by anyone. And you'll be glad that McVeigh stupidly criticized Jones, endangering McVeigh's legacy, so that more facts about the case could come out.

These two novels by Steven King (one under his Richard Bachman psuedonym) are based on an interesting idea. Take the same set of characters, and put them into two completely different and totally unrelated stories. Not only are the human characters the same, the evil being they must fight, Tak, is the same in both stories, and both stories involve the town of Desperation, Nevada and the suburb of Wentworth, Ohio to a greater or lesser degree. By unrelated here, I mean one story is not the continuation of the other, it's as if they happen in parallel universes.

In Desperation, the humans are trapped in a small western mining town in Nevada where Tak has taken over and killed off most of the town's residents. Tak has apparently selected a random group of humans to keep alive to be used for it's own purposes, but it is unaware of the fact that one of these humans, a young boy, has a connection to a higher power than itself (i.e. God) which is intent on thwarting it's plans. In the story, King attempts to wrestle with serious theological questions, particularly with the problem of evil and suffering. While not overly profound, the book does have some moral and spiritual depth to it and is surprisingly Christian friendly.

In the Regulators, the creature Tak takes over the mind of a young autistic boy, and then uses images in his mind, gleaned from old western movies and Saturday morning cartoons to terrorize and demolish a suburban Ohio neighborhood. While The Regulators could be seen as a commentary on the effects of popular media and television, there really isn't the same kind of pointed moral and spiritual questioning that is found in Desperation. It's just an entertaining story.

Though I think Desperation is the better of the two books, I enjoyed them both, and found them both to be gripping reads. King really is a good story teller with some interesting ideas, and is also good at creating a sense of place and mood. He is also good at creating interesting, realistic, sympathetic characters. Both stories are pretty violent, especially The Regulators, and some readers may be put off by a fair amount of bad, sometimes sacreligious language and crude subject matter. The stories are still interesting and enjoyable though, and Desperation especially carries a sense of moral weightiness that, for me, helps to define good writing. If you read one and enjoy it, you'll probably want to read the other one as well to see how the different characters fair in both stories.

After reading some of the reviews listed on Amazon I couldn't believe anyone who enjoys Stephen King did not enjoy The Regulators and Desperation. Someone wrote that he showed no imagination by using the same names. It simply showed the genius of his writing. One book was written under Bachmann, the other written by King. Two books written like parallel worlds, mirror images of each other. I couldn't put either one down.

Desperation was the first Stephen King book i read, a few years ago, and since then I've gone on to read `Salems Lot, The Stand, Bag of Bones, and, of course, The Regulators. Although i can't say, like someone already rated, that the plot jumped around so much that you couldn't follow. Desperation was my first King book and i found it very enthraling, and The Regulators simply added to it all! Yes, he uses the same characters and a few more, but there's a different setting, a new "host" for Tak, and an entirely new form of writing involved. If you have not read either of these books, i suggest to start with Desperation, and if you are a fan of King's older works, i am almost certain you won't be disappointed.

This book is simply dreadful. The premise is so implausable as to be laughable. Engineered Nazi zombie with steel teeth and claws gets loose after being preserved in a u-boat for fifty years, to terrorize the coast. An author not named Benchley would not be able to get this published. Apart from some well written passages about the water, marine life and coastal towns, the book is bad. I mean, it is really bad. The title is deceptive (white shark being the code name for the Nazi Zombie) and the main charactors are so wooden as to be painful. One has to respect Benchley as the master of his genre, but he would have been better off having typed this one to re-read it and toss it in the garbage. He didn't, and there it is. Please do not read this book. Please do not buy this book.

Duh dum...duh dum... Just when you finished 'Beast' and wondered if Peter Benchley knew how to write anything else but sea tales of monsters and scantily clad swimmers comes his latest, 'White Shark'. This book is a cautionary tale about what happens when you mix early Nazi experiments in genetic engineering ('Vee vill mix man and the shark and together vee shall rule the world!') and a small waterfront community. If this smacks of similarities between 'Jaws', a cautionary tale of what happens when you mix hungry shark with a small waterfront community and 'Beast', a cautionary tale about a hungry squid and...you get the idea...you've stumbled upon the first problem with Benchley's tale. We've been here before and halfway through the novel, you start to wish for something different. It isn't that Benchley doesn't try hard. Many paragraphs have an air of suspense to them, especially the ending climactic scenes. However, far too often, it is simply a whiff of what could be rather than a match for some of Benchley's better work. Go read 'Jaws' again if you want a taste of true thrill fiction.

WHITE SHARK is perhaps one the best written dead ends in history. Although packed with ideas, some adventure, and many, many ten mile wide close calls, by the end of the book you are literally left wondering what is it you just read. Its pacing and narrative are written like the tides breaking on the shore... it rolls in, it drags out, repeat until end of novel. Every so often the waves bring up something that sparkles, but it never truly shines through. The creature here is a crackjack idea (although a lift from the film SHOCK WAVES), but Benchley spends little or no time with it. And the major players in the book are made from the thickest carboard there is - they hold no surprises, and are so routine that Benchley never breaks a sweat when writing them, because we already know them and know what will happen to them. The hero and herione will get together at the end (they do), the sidekick will pull through (he does), the son will find his first love (he does, a deaf girl with telepathic powers which Benchley mentions once, and then drops, almost like she was going to play a larger part in the story, but Benchley found it too time consuming to continue with), and the monster will die (it does, pretty quickly and easily). Not his best work. For fans, it's worth the read. For those just picking up Benchley, start and stop with JAWS.

The book covers too many topics and just few are developed in deep while others are superficially introduced because not yet standardized at the time of print. The book claims it covers the following topics: XML, XSLT, DOM, DTD, SOAP, XLink, XPointer, XPath, WAP, WML...and more; but just XML, Schemas, DTDs and SOAP could almost fit the book's size.

Chapters don't follow a very logic thread and it doesn't deal enough with very relevant subjects. Wrox probably planned to make this book the XML bible but I think they are far from the target.

The XML declarative language, with its adaptability and expressive power, is continuing to become the language of choice for reporting and classifying information. XML is a formal grammar that captures the syntactic features of a document type definition, and its properties, syntax, and applications are discussed effectively in this book. It covers XML as formalized by the W3C and the authors show how to use XML in Web-based and database applications. Readers who have developed applications in HTML will probably view XML as somewhat more abstract, since the visual representation of the content of a document is not emphasized in XML. Readers are expected to have a background in HTML, JavaScript, Java, and ASP in order to read the book. Although XML can be learned by reading the W3C specifications, these documents are frequently difficult reading, and this book makes the learning of XML much easier than reading these specifications. They include the W3C specifications for XML 1.0 in an appendix to the book for the interested reader. The book is a little dated, since the W3C has been updating XML specs since the time of publication (especially with regard to schemas), but there is a 2nd edition coming out soon.

In Chapter 1, XML is introduced as a mark-up language and its inherent extensibility emphasized. This is followed by a detailed treatment of XML syntax in the next chapter, with emphasis placed on the hierarchical nature of XML. The authors do include a discussion of Processing Instructions (PIs) for users who want to use XML in this fashion.

Document Type Definitions (DTD) are the subject of Chapter 3, where the authors communicate effectively how DTDs formal grammar is used to specify the structure and permissible values of XML documents. The formal DTD structure is discussed, and the principles behind writing DTDs are effectively outlined. They also discuss the problems with using DTDs.

Data modeling with XML is discussed in the next chapter, with information modeling via static and dynamic models treated in detail, and the authors carefully distinguish these two approaches. The actual designing of XML documents is given a nice overview as well as the role of schemas in XML. This is followed in Chapter 6 by a discussion of the (tree-based) Document Object Model, which overviews how XML documents can be accessed by various programs. Some helpful examples are given on how the DOM can be used to create an XML document programmatically. An alternative way of processing an XML document is discussed in the next chapter on the (event-based) SAX interface. The authors outline in detail the benefits of using SAX rather than DOM. In Appendix B the reader will find the Internet Explorer 5.0 XML DOM 1.0 W3C specifications. In addition, in Appendix C, the specification for the SAX 1.0 interface is given.

The shortcomings of DTD are addressed in terms of XML Schemas and namespaces in chapter 7. Since this book was published, XML Schemas have reached W3C recommendation status as of Nov 2000. The authors give a good overview of namespaces and schemas, with helpful examples. This is followed in chapter 8 by a discussion of how to link and query into XML documents using the XML information set, XLink, XPath, XPointer, XML Fragment Interchange, with XLST covered in the next chapter. For database applications, the authors outline the differences between relational databases and XML documents. A very detailed treatment of how XLST transforms the source document is given, and the authors compare XLS and DOM transformations. An Internet Explorer XSL reference is included in one of the appendices of the book.

More details on the relationship between databases and XML is the subject of chapter 10, wherein the authors show how to store XML and how data can be communicated between different servers using XML. The issues involved when moving data from RDBMS to OODBMS or from Oracle to Sybase, are discussed by the authors. This is followed by an interesting discussion on how to use XML as a distributed component model for server-to-server communications via XML-Remote Procedure Call and Simple Object Access Protocol.

E-commerce applications are discussed in the next chapter, with EDI and its improvement via XML. The business markup language cXML , which allows business to business electronic commerce transactions across the Internet, is also treated in detail.

The authors then finally discuss how to render XML documents more readable and pleasing for the viewer in the next chapter using the style languages CSS and XSL. The discussion is really interesting, for the authors dig a little deeper into the foundations of style languages. The discussion of style languages as rule-based languages is particularly illuminating.

The next chapter is very interesting and its inclusion is actually very surprising, namely a discussion of the Wireless Application Protocol. The authors give an introduction to the Wireless Markup Language and WMLScript. The book ends with four useful chapters on case studies for data duality, distributed applications, a book catalog information service, and SOAP.

There are many applications of XML in many different areas, such as CellML (proprietary) used in cell biology, CML (Chemical Markup Language) for molecular chemistry, IML (Instrument Markup Language) for control of laboratory equipment, BSML (Bioinformatic Sequence Markup Language) for gene sequencing, and MathML for formatting of mathematical equations. I find XML an extremely powerful approach to information reporting and I am currently developing a package called NMML (Network Modeling Markup Language) for use in reporting results in simulation and mathematical modeling of networks, and FMML (Financial Modeling Markup Language) for use in reporting results in the modeling of financial instruments. This book, along with the W3C specifications, has been a tremendous help in the development of these applications.

Awesome "self-teach" book. I've been programming for years, but was new to XML and needed to start using it in my applications, so I had just the very basic concepts of what XML was before I started reading. This book is very complete, gives tons of practical examples and guidelines, and provides many external references. This is the ONLY book you will need to learn XML effectively on your own.

As others have stated here, the only real downside to the book is that it repeats many concepts more than once, so it is NOT the best choice for a reference book.