In Effective COM, the authors, Don Box, Keith Brown, Tim Ewald, and Chris Sells, offer 50 concrete guidelines for creating COM based applications that are more efficient, robust, and maintainable. Drawn from the authors' extensive practical experience working with and teaching COM, these rules of thumb, pitfalls to avoid, and experience-based pointers will enable you to become a more productive and successful COM programmer. These guidelines appear under six major headings: the transition from C++ to COM; interfaces, the fundamental element of COM development; implementation issues; the unique concept of apartments; security; and transactions. Throughout this book, the issues unique to the MTS programming model are addressed in detail. Developers will benefit from such insight and wisdom as: Define your interfaces before you define your classes (and do it in IDL) Design with distribution in mind Dual interfaces are a hack. Don't require people to implement them Don't access raw interface pointers across apartment boundaries Avoid creating threads from an in-process server Smart Interface Pointers add at least as much complexity as they remove CoInitializeSecurity is your friend. Learn it, love it, call it Use fine-grained authentication Beware exposing object references from the middle of a transaction hierarchy Don't rely on JIT activation for scalability and much more invaluable advice. For each guideline, the authors present a succinct summary of the challenge at hand, extensive discussion of their rationale for the advice, and many compilable code examples. Readers will gain a deeper understanding of COM concepts, capabilities, and drawbacks, and the know-how to employ COM effectively for high quality distributed application development. A supporting Web site, including source code, can be found at http: //www.develop.com/effectivecom. 0201379686B04062001Consider the scenario in which object C holds a weak reference to object B. If C has other parties holding references to it, ita#39;s possible for B to go away while C still lives, leaving C with a dangling pointer to B. One hopes that C doesna#39;t share ananbsp;...
|Publisher||:||Addison-Wesley Professional - 1999|