Read the Microsoft documentation instead. This book is a thinly disguised rip-off of the Microsoft documentation padded with examples of dubious value. In 590 pages this book manages to add no value or information beyond the original documentation. That's quite an achievement.

If you want to learn ISAPI...think again. This was "hot" 2 years ago...now it is all but dead.

ISAPI's big promise was better performance and memory usage...ironic that it has now fallen in favor to the biggest performance pig of all web applications...ASP. In an age of fast machines and small web apps, rapid development and ease of use wins out over performance.

ISAPI is hard to learn, harder to get right, unstable, bug ridden (if written in MFC) and surprisingly inflexible.

Look, you're a smart person. You want to do the right thing. You don't need to subject yourself to the torture of learning ISAPI. Only hard-core programmers who are tasked with writing a custom web app that is going to get some VERY heavy traffic should even bother with ISAPI.

So why did I give this book 4 stars? There are no good ISAPI books out there. This one has the most information in it and will allow you the best chance to actually develop something that works. Get this book and hit Genusa's (now dusty) ISAPI site. Also spend a lot of time in the Microsoft knowledge base...there are plenty of workarounds and bugs to learn about too.

Keep in mind that with ISAPI you had better be a damn good programmer. If your DLL ever crashes...bye bye web server. This is harder than you think if you are doing "serious" web programming which includes database access.

Smart managers will not allow mission-critical web apps to be developed in ISAPI by a web punk who has never done this before. Do everyone a favor and get a clue. There is a reason why nobody is doing this stuff anymore!

Game over. Go home and don't look back. Go off and learn ASP and Cold Fusion like a good little web programmer. You will have a marketable skill and will actually get things done.

ISAPI is Microsoft's approach to adding capabilities to web serving. There are only a few books that describe how to use ISAPI. This book is the best of them, because the author: 1) provides examples in both C and C++, and 2) compares ISAPI with CGI solutions. Unfortunately, ISAPI is a complicated subject, so more and shorter examples would help elucidate the reader.

This book is awful! I know the fundamentals of programming in Flash and ASP.NET so regardless, if you are advanced or know the basics this book is still AWFUL!!! Trust me do not buy it! The Poll in the first chapter does not even work. I went to peachpress to find the updates for the book and the Poll sill will not work. The book constantly points to the CD and the CD is missing the files the chapter is pointing to. The Poll.XML on the CD does not match that in the book, I mean come on! This was all before I even got through the 1st chapter! ...

... I am sure that some of these examples worked, but only in the head of the author who authored the chapter. I am so upset about this one; ...

I couldn't agree more with the reviews that have already been posted. This book assumes WAY too much knowledge and leaves large chunks unexplained (like the #include .as files that don't even get a mention...)

The layout is sloppy and poorly thought out - eg they have 2 pages of code and THEN they describe what is happening in the previous 2 pages, requiring you to be costantly flicking back and forth. Simply repeating each line of code with its explanation would have made it so much easier to read (authors should check out "OOP with Actionscript" to see how it SHOULD be done).

The code that is included is full of stuff like

gotoAndPlay("whatever");//used to be gotoAndStop

making it obvious that the author hasn't even bothered to clean up their code before slapping it in the book. When covering a complicated topic like this, having comments that reveal the "mistakes" that the author made along the way is confusing, annoying and inexcusable (not to mention very revealing about the amount of effort [or lack thereof] that went into this book).

Save your money

cheers

I came into reading this book with very little Flash experience. All I'd done was simple timeline based flash movies. I chose to read this book to help get an understanding of Flash's capabilities and how to further the skills I had, enabling me to create dynamic content in my Flash movies.

I thought this book was unique in that it didn't get into the hows and whats of Flash, but straight into some very interesting example code. It also doesn't focus purely on Flash, but integrating flash with web application server products like ColdFusion and ASP.

While I'd never be able to create any of these examples on my own, it was quite cool being able to walk through each code example and see how everything works. Some of the Flash code was a bit hairy to follow, but they did attempt to explain it. Rather than learning what the code meant, I just read the comments stating what the code does and moved on. Unless you're experienced in flash, you won't be able to follow the code line for line. However, wading in example apps above your capabilities is a great place to learn.

Each chapter is a different example application, focusing on a dynamic backend. Some use ASP, some use ColdFusion, etc. So you can pick your middleware of choice and they'll be an example here for you where you can view both the Flash code, as well as the code it interfaces with to achieve dynamic content.

I wouldn't recommend this book as your soul source of Flash instruction, but it is a unique book rich with very usable example code. I didn't learn much Flash actionscript from this book, but I did come out of it with a good understanding of how Flash can be dynamic, using XML to communicate back and forth to your scripting language of choice. If that's what you're after, this might be a good book for you.

Overpriced for what you get and only valuable to the firms designing highrise and industrial complexes. Find a copy and review for yourself before you buy.

The AIA should be embarrased by their publishing this "book". At less than forty pages of information it hardly qualifies as a book. Note that the information it does contain is fine but it certainly does not deliver good value for the money. The price is outrageous especially when you add amazon.com's fair shipping and handling costs. I expected more from an professional organization like the AIA. Note in the above description it doesn't identify how many pages the book contains as do most amazon.com descriptions (I get junk-mail thicker than this one). I understand that books like this have a limited audience and that the costs of production and distribution are correspondingly high. That being understood, a price under $5.00 would be more appropriate. I regret to say I will be weary of any other publications of the AIA Press.

As a CAD instructor and design professional I've been using the Master CAD Layer Guidelines since 1998. I find it to be a very effective tool for teaching beginning and intermediate CAD users the proper way to use layers for industry. In that regard it is invaluable. However, I am embarrassed by the exorbitant cost of the publication. Originally, I purchased this "pamplet"--which would be a more apt classification at a mere 40 pages--for $19. Over the years little information has changed, but the cost has skyrocketed. I can't imagine why. Excellent resource, terrible value for the money. I recommend an office buying one copy and passing it around, rather than supply everyone a copy. That's what I am reduced to do for my students. I thought AIA promoted well-educated, knowledgeable professionals, but is that at a cost that only the elite can afford? Come on, guys, get with the program.

I was an English major and have been a teacher for 16 years, so when I throw away a book, there's a problem. The little girl in the story, Whitney, gets so involved in her activities or her imagination that she sometimes doesn't hear her parents calling her. When the family goes to an amusement park, her parents accidentally leave her there. The book is written from the "real-life family episode" of a Christian singer, Michael Smith and his wife. They have 5 children, so you could see how they might leave one at an amusement park. My problem is that when they go back and find the child, it is Whitney who has to apologize to her parents for not "paying attention". The parents NEVER apologize to the girl for leaving her in a frightening situation and not arriving back to pick her up until it is night time and the park is closed. I am active in my church and teach Sunday school, so the parents' prayers for Whitney's protection and safety are fine with me. I just think they should have told her they were sorry they didn't keep her protected and safe themselves. That's the parents' job, after all. I would have preferred a book that, in the end, showed the parents' admitting they weren't perfect rather than putting the responsibility for a very scary experience onto the child. If there were a zero stars rating, I'd give it to this book.

A simple yet engaging tale of a family reunion which decides to go to an amusement park. Whitney does not pay attention and . . . well the story goes from there. My son loved the illustrations and the story was right on his level ( 4-5 year old). There actually is a religious end to the story, but considering the author, I thought God would be mentioned more.

I wanna search some good resumes inorder to prepare mine

I have just read this book for an exam in political science in University of Turku, Finland. I dont think I am the right person to review this book, because I dont remember any of it. All the time I was supposed to read this nice book I spent drinking coffee, smoking cigarettes and eating with my friends, and off course terrorising my friends with my useless e-mail. I will never read another book about international politics. I'll rather spend my time practicing my computer and internet skills.

We were trying to replace the heater core, the instructions were foggy to say the least. Further repairs or maintenance just as foggy, its a good book if you have a lot of experience with repairing the vehicle and don't need a how to. Amazingly the "Ford Tempo Mercury Topaz 1984-94" book by Mark Christman, which is by the same company, was a lot better for repairs and maintenance. But neither book helped with replacing the heater core, we eventually used other resources for more ideas on how to actually get to the heater core to get it out.

I've used this book for nearly three years now, and keep wondering why I go back to it. (Actually, it's because it's the only Tempo/Topaz book I own.) I have found several major errors in the illustrations, usually due to showing a 2.0 engine setup as a 2.3 or vice versa. Some instructions, like how to change a water pump, are just plain wrong. Electrical schematics, particularly of the instrument cluster are sketchy to the point of being useless when troubleshooting anything other than a hard failure. I suspect that much of the text in this book was a quickie cut-and-paste job of info that pertained to these same components as installed in other Ford products. It really doesn't do justice to the model-specific problems of navigating the limited space of the engine compartment or tracing an intermittent electrical circuit. Proofreading was spotty at best. It's better than doing a repair job blind, but not by much.

Chilton's Ford Tempo and Mercury Topaz Repair Manual 1984-94 is not for the average car owner. It is probably not even for the average mechanic. It is written in difficult language and at times seems to display unnecessarily complicated methods of performing simple tasks. From beginning to index it offers low quality information and instruction. There are too many diagrams and not enough photos. The photos available are poor. Overall this book was not very useful to me. I have used the Haynes manual for the same car and found it much more useful.

This text has numerous flaws whcih I will simply list: 1) There are numerous questions with more than a single correct answer and no "best" answer. 2) Often the answer key does not correspond to the question's numbers. For instance "A" is the correct answer, but in the explanation "B" is described as the correct answer. 3) There are pediatric questions in the adult medicine section. 4) Maybe 40+% of the surgical section is orthopoedic. 5) Some answers are suspect. For instance, some trauma questions provide no best answer. Which bad aswer should I pick? 6) Often it is unclear how to answer questions: i.e respond "true or false" to each possible answer, or single best answer. 7)Often questions are clumsily worded, with unclear directions.

Overall, the frequent mistakes do not inspire confidence in the reviewer. There is no clear sense that this review book might in any way correspond to the board exam. I wouldn't buy this book again!

The adult medicine section was extremely brief in content, had a lot of typos, and did not reflect the content of the shelf exam which focused on fatigue, shortness of breath, HTN, stroke, etc. The pediatrics and geriatrics sections were decent, but again the shelf focused on developmental behavior (not only on a single milestone).

This textbook is recommended in one of my first year modulesin the University.It is very difficult to understand and totally useless to someone who is trying to learn java with no programming .But I guess for an experienced programmer,the book could be of some use, because of its explantions and different usagesof java.But that is when you have mastered the basics.This is really not an introductory text.I found the text java for students much better suited for my needs

This book should be called "How not to teach Java". No index, terrible examples, confusing table of contents...do i have to go on?

This book was recommended for my course. It is very poor indeed. The first few chapters which cover the basics aren't too bad, but things very quickly become awfull. Unnecessary complications are introduced into simple programs, and not explained at all well. The author plunges into each chapter without introducing any basic concepts. In the graphics chapter, nothing is said about setting up a graphics object - the second page is already talking about methods in the package. Not only has this book not helped me one bit in learning Java, it has actually hindered it. You have been warned.

³ª' Çѱ¹ »ç¶÷ÀÌ'Ù. ¾ÆÀ̽ºÇÏÅ°°¡ ³Ê¹«³ª ÁÁ°í »ç¶ûÇÑ'Ù ³ª' ±¹°¡'ëÇ¥À» °ÅÃÄ ÇöÀç' °íµîÇб³ ÄÚÄ¡¸¦ÇÏ°íÀÖ'Ù ±×·¡¼­ ¼±ÁøÇÏÅ°¸¦ ¹è¿ì°í½Í¾î¼­ ÀÎÅ׳ݸ¦ÀÌ¿ëÇÏ¿©¼­ ÇÏÅ°°øºÎ¸¦ÇÏ°í½Í'Ù