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.

If you want to read one of THE dullest, stuffiest, not to mention stylistically ghastly books in all of art history, please read this one. These writers confuse ambiguity and meanlingless hodgepodge for intelligence.

More regurgitated destructive orthodoxy from the arid soul of an academic hack, it's all here every careerist leftist's cliche there is. The arrogance of the previous reviewer could only come from a button down Yalie politically correct snob.

This is the textbook used in Yale's introductory course to 19th century French art, and is considered to be the industry standard for surveying the period.

I think this book was too wordy for a text book. I believe this Accounting book should have had more examples and explanations of the examples to be able to work the problems at the end of each chapter. When you are trying to understand what the numbers really mean "which is the name of the book", I think you should go into more detail as to what the numbers really do mean and also how to get those numbers.

There are a lot of poems in here but you look far and wide for something really good. I mean, sure, there are the people we already knew were good -- C.K. Williams, Eavan Boland, Frank O'Hara and et cetera et cetera -- but with a book this big you want a few surprises, you want to find some new stuff you didn't know about before. And for me, that didn't really happen. Philip Larkin's "Aubade" is maybe the best poem here -- and maybe the best poem about death ever written -- though what it's doing in a book of AMERICAN poetry I can't figure out (I guess it was just too good to exclude). They put Seamus Heaney in, too, which makes me wonder why they left out Paul Muldoon -- he's been living in New Jersey for years now, and writes poems as good as anything in here (and better than 99% of it). Go to your local bookstore and look through this monster -- maybe you'll have better luck than me, and find something thrilling -- but don't buy it.

I received the scrapbook a week before christmas and I was so excited. I thought it would of showed pictures of how they made the mummy... maybe a couple of pictures and about the CGI and everything but it only did a resume about the movie "The Mummy" and say a couple of egyptian facts here and there. Also, I only found 1 quote from an actors point of view (from Arnold Vosloo) in this VERY THIN scrapbook of 48 pages and they didn't even write his name right! His pictures were sexy but they could of embellish this book with a bit more information and quotes from the actors themselves...

i'm rating this book at 2 stars mainly based on its age. it holds little value now for most unix security curious admins. however, looking through it again i realize that it hits most of the basics (at the time) well. it covers filesystem and access security reasonably well, and the example code is reasonably correct in spirit, if not always in practice.

of historical value only, not reccomended.

This book teaches me on important thing, which is 'Make early failure a learning, not fatal experience', and 'Treat triumphs as fleeting'. However, vision should be remained the same over time.