I bought this book, and I found that Apache did not have the Version decribed in this book available for me to download.

This book was good for me only with the basic command just to make a web site up and running, but was not good for me in configuring CGI, access control, and other complicated usages.

Apache has updated its version frequently. So, you will have difficulties using instructions from this book with Apache of today versions.

Get newer Apache books if you can.

I also wish the author writes a new and updated version though.

Well , it helps me start from nothing-i-know-about-apache and now my site is running as i expected.So cool and smooth. No error found in the book. But anyway curious web admin will get benefit from more-detail and real world-based implementation ,for example, all modules usage in dept, custom source compliation on win32 etc. (I know that this info could be found in online docs ,right? but i'd love to read from text book) I love this book but still wondering why the authors include (p.270) pics of how to enter proxy server setting in NS/IE ? Is it that important?

I'd recommend this excellent book! This book presented the steps (with great explanations) that I needed to easily set up the Apache Server. It has breath enough for more expert users, too. Its content was equal or greater than the O'Reilly press's "Apache Definitive Guide" (which I purchased first and could not understand).

Hollywood, 1941. Screenwriter Keith Moody is about to hit the big time with the dramatization of his cousin's heroic war exploits. Greg Matthew's first mystery is a chronicle of Moody's experience, chock full of quirky humor, nasty characters and implausable plot twists. Its satirical depiction of the movie biz, our weak but willing hero's Faustian dilemma, and a unique love interest are presented in a narrative that soars above the messy plot, creating a portrait of a corrupt and totally fascinating world, as Far From Heaven as possible. Weird and wonderful--I LOVED it

Matthews has written a mystery novel that is a joy to read. Smart, funny, unique, and featuring literature's greatest reluctant hero since Jean Casson from Alan Furst's "The World at Night," and "Red Gold." I've already purchased the second novel and anxiously await the further adventures of Keith Moody.

This book is redolent of Salenger's Catcher In The Rye. It's about 16 year-old Burris Weems, who reminds me a lot of Holden Caulfeild, but he's not such a whiner. He's very intelligent and highly observent, but lacking in ambition. He stole a microcassette recorder from a Radio Shack on the day he learned that he'd failed the last semester, and will be held back a year. He begins talking into it....and that is how the book is written. He talks about his Mother, who sells paintings of Jesus and Elvis on black velvet, and of his cab-driving sister, and of the Father he never knew, who died in Viet Nam, and how he was born the very moment Neil Armstrong stepped on the lunar surface and blew his famous lines, and such. Then he meets a guy at a Summer job in a box factory, who introduces him to his wife and her transexual father, and unintentionally sets the story into high gear. As he talks about all these things into his mini-recorder there is no hint of the wild adventure ahead, so this book will catch the reader off guard at every twisted turn, and provoke explosive laughter out of the blue. This book is a rare treasure, that few know about. Matthews has written one hell of a book, and it deserves more recognition. Upbeat, witty, funny, shocking, and original.

I just finished this book recently. I've been a big Matthews fan and loved Power in the Blood and One True Thing. This novel was something rare. It was pretty much a blatant ( ) of Catcher in the Rye, but he pulled it off so well that I think it may have been even better. The cast of odd characters are fantastic and Matthews masterfully holds up the structure of the novel(The whole thing is Burris Weems speaking into his stolen tape recorder). If you haven't read anything by Greg Matthews start now. You won't be dissapointed. He's probably the best kept secret in literature today.

proofread your book.

I reiterate the first review.

How could any editor in his/her right mind let any book go to print with this many mistakes? This thing is packed with typos, misspellings, code errors and downright wrong information. There are so many errors, you'd think it was written by Microsoft!

I haven't finished the book yet, I'm currently on Chapter 26. I'm slogging through it though, page by page, because there is a lot of good information in it - enough to warrant the two stars. But please, if you're taking the time to write a book, then hire an editor that can proof it, including the code, and fix all your screwups. A typo here or there is forgivable (I'm sure there's a few in this review); a coding error or two is forgivable; but producing a book with this many mistakes, then selling it for a dear sum, is just plain wrong. Oh wait, Microsoft does that with their software, so I guess it's commonplace and accepted.

As for the good parts of the book, it does cover many different areas, and I like the fact that it tries to help the reader with dynamic applications and Dreamweaver's excellent database functionality. I am an advanced user of Dreamweaver, but bought this to expand my knowledge in the dynamic webpage field. Even with my strong background, I still found many new things in the first few chapters that helped me out right away. That gave me an initially positive response to the book, despite the typos and other errors I spotted.

It's nice that the authors use Mac screenshots and include plenty of Mac-specific information. If you're still using Windows to do design work, then you're in the wrong profession.

The book gives a good introduction to web applications and setting up a web server, including integrating it with a database and the use of middleware. However, all the mistakes in the book made it extremely difficult to actually learn something. I made the mistake of trying to set up Apache, Tomcat, PHP and mySQL on a Windows system, and spent many hours on the web trying to fill in the gaps that this book leaves out. I should have followed my initial intuition and went to linux or Mac to do this. The authors of this book should know that there's still a lot of poor souls that use Windows, so they should have included information for both Unix and Windows. For example, the Perl shebang statement in the book is for Unix - they should have both the Unix and Windows flavors.

The book covers the asp and asp.net world OK, for those that wish to pay the Microsoft tax for things they could otherwise get for free. So if you (or your company) don't mind the extra expense of Microsoft, then you can learn the basics from this book.

All said, I would treat this book as a great way to get started on Dreamweaver or to learn some of the more advanced functions, but to get into PHP, mySQL, Perl, JSP or some of the other topics, you really need a book dedicated just to those topics. I'm not saying that as a criticism of this book, becaust I think that's what the authors intended - it is a Dreamweaver book after all, not a book on those other subjects.

But there are just way too many mistakes in this book to make it completely useful. Here's an example: on page 552, they tell you that a PHP array is numbered beginning with 0 - the first element is numbered 0, the second is numbered 1, etc., and give a sample array with five elements. This sample array should be numbered 0 through 4 for the five elements, but in the very next line, they refer to the fifth element as element number 5!

Another example is on page 541, item number 5. They tell you right at the top of the page that Java is case sensitive, then they go and enter the code with the wrong case (string instead of String). To make it worse, they used a curly bracket instead of a semicolon.

-easy read, with lots to read.
-intermediate to expert, it is a how-to book not a step-by-step.
-good content on database developement.
-no e-book, no dreamweaver eval, download samples and tutorial off of website, no biggie.
-most screenshots are from a Mac.

I loved the narrative of this book. It was witty, entertaining, and, as far as characterization goes (minus the vampire aspect!), extremely realistic. It was a thoroughly entertaining read, right up until the last 10 or so pages, where the story fell apart-- almost as if Anderson threw it together at the last minute. The ending was rather hokey, but I think this novel will appeal to most.

The whole story was great! It was as if there were vampires huddled around you as you read! It makes thirsty like a vampire as your reading and can scare the pants off you! Its great And I would reccomend it to anyone except of course for little kiddies! Its worth every penny and then some! If I could give this book 1,000,000 stars i'd give it!

I was amazed at this powerful story of a young man confronting forces so far beyond his control that every plan he makes, every instinct he has absorbed from the horror movies that he and his friends constantly discussed prove to be woefully inadequate. _Thirsty_ is an amazingly example of a genre writing against itself.

On tap of that, I liked the tone of Anderson's first-person narrator -- sarcastic, confused, but also shy. He's a 15- or 16-year-old guy trying to figure out how the world works -- and if that weren't enoough, he's beginning to suspect he's a vampire and a pawn in a mysterious battle between the Forces of Light and Dark.

I'm going to read everything M.T. Anderson writes for the rest of my life.

I am disappointed in the actual code commentary, it does NOT do a good job of explaining the code. Most of the time the commentary does nothing more than tell you what a function does - and it is obvious from the name anyway. Apache has a lot of standard programming conventions and internal libraries. I think those should have been covered first and in depth. It would make the Apache source code much more understandable. I read through the first chapter or so of Linux Core Commentary and it seems much more well written.

i bought the book to underdtand how apache worked interanlly. the book does a good job of that. however the the code commentry is pretty disjointed. the compilers have done a excellent job of putting together this. we should see more of such types.

Good job explaining the server code.

I really enjoy the Using Series, and look for them whenever I want to learn more about a certain topic. However, this book is deplorable. It is not made for anyone looking to write their own code, or anyone who actually wants to program. All this book tries to do is show you how to use someone else's code. I do not mean another module, such as the infamous CGI.pm moudle, but rather using another script and "tweaking" it for your needs. It also does not seek to explain the theory behind the code. I was also quite disappointed in how it was organized. The Using Seies are good books, but this one doesn't belong in the family. There are much better books out there that will serve your needs.

I found this book to be hard to read and poorly written. The examples are very difficult to follow because most are only code segments not the full code. This makes it very diffcult to follow. As any experienced programmer will tell you "Nothing helps more than a good example.". This book is highly lacking of good examples. I have several years of experience with programming in several languages, which allowed me to fill the gaps in the examples, how ever a beginning programmer would be lost. In conclusion I do not recommend this book to a programmer of any level.

I found this book to be hard to read and poorly written. The examples are very difficult to follow because most are only code segments not the full code. This makes it very diffcult to follow. As any experienced programmer will tell you "Nothing helps more than a good example.". This book is highly lacking of good examples. I have several years of experience with programming in several languages, which allowed me to fill the gaps in the examples, how ever a beginning programmer would be lost. In conclusion I do not recommend this book to a programmer of any level.