This book is a fast-paced tutorial to developing ColdFusion applications using an object-oriented programming approach. Complete with code examples that can be altered and applied to your application and careful explanations, this book will guide you through your first interaction with object-oriented programming within your ColdFusion applications. If you are a web developer wanting to implement object-oriented programming with ColdFusion, then this book is for you. If your goal is to get a good grounding in the basics of object-oriented programming concepts, this book is perfect for you. No prior knowledge of object-oriented programming is expected, but basic knowledge of ColdFusion development skills is assumed.
This book was a very quick read - I read it cover to cover in a little more than two and a half hours. Still, it manages to pack in a very succinct and clear explanation of the basic building blocks of OOP in ColdFusion: CFCs and the "Bean" paradigm.
If you're already familiar with the technical aspects: What CFCs are, how to write them, and how to instantiate and use them; then you can probably skip directly to chapter 4, where the less tangible aspects of OOP are covered: Inheritance, Polymorphism, Composition, and Aggregation. These are the concepts I was hoping to expand my understanding of by reading this book and while they are all covered and perhaps done justice, I would have liked to have seen a bit more content dedicated to them. As it is, all of these topics share a single 22 page chapter. After which, a lengthy discussion of DAOs, Gateways, and Services finishes out the book; which may do more harm than good.
As a veteran of the "5-to-1" arguments (is it necessary to create a bean, dao, gateway, service, and value-object for every entity/table?), I tend to stray away from informing people about all of the intricacies of each of these objects for fear of understanding being mistaken for promotion. I hope people don't read this book and take his explanation as advice, and start creating all of these objects unnecessarily again.
For as short a book as it is, I suppose it's a fair distribution of content, but as I said, I would have liked to see a bit more discussion around the 4 most often confused concepts of OOP and less around DAOs, Gateways, Services, etc.
My job involves more involved programming than is outlined in this book, but I learned as I went so I didn't have much theory to back up what I'd picked up on the job. This book did fill in a few gaps in my knowledge, especially of the vocabulary of OOP and how the parts fit together in theory.