COM Marshaling
COM is becoming ubiquitous. You can’t avoid it. As you adopt COM as a lifestyle, design paradigm, or object model, you will likely want to place objects in more than one address space, or at least create objects from more than one thread. This course explains more than you ever wanted to know about how COM shares objects between threads, processes, and eventually, host machines.
This seminar exposes the guts of the Component Object Model, demystifying the relationship between proxies, stubs, custom and standard marshaling, and dynamic invocation. Microsoft defines roughly 70 standard COM interfaces or data types as part of OLE that allow objects to exist in multiple address spaces and/or multiple host machines. Developers that fully embrace COM as an object integration substrate normally require custom COM interfaces for which Microsoft cannot provide a priori marshaling support. COM provides a rich architecture for marshaling interfaces across process boundaries that allows the class implementor to control the distributional characteristics of a given object. Definitely not for the timid or faint of heart!
Experience programming in C++ is mandatory. An understanding of the material covered in Essential OLE: Inside the Component Object Model is essential.
You will have an intensive understanding of COM, but may be incapable of normal human interaction thereafter.
- Marshaling Basics
- The Proxy/Stub Architecture
- Implementing Proxy/Stubs using IDL
- Implementing Proxy/Stubs Directly
- 16/32 bit Marshaling issues
- Custom Marshaling
- Automation and Dual Interfaces
COURSE NUMBER FW600
2 days. $ 995. Course includes study-kit, PC for lab exercises.
