Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 241
  • Last Modified:

The concept of COM

I still confuse with the concept of COM (Component Object Model), because it is similar with OLE concept.
Can any experts help me to make the concept clear to me?
0
stinger_60284
Asked:
stinger_60284
1 Solution
 
ThaddyCommented:
OLE, object linking /Embedding is part of the COM specification, although it's actually older technology.
COM is centered around the idea of 'interfaces'. An interface is an abstract 'contract' of how an object behaves when interacting with other objects. It says, 'Hey, if you ask me in a certain way, I Guarantee you that I will answer/behave in a certain, predictable way, always,period'.
The underlying implementation code to an interface can vary a great deal on the same interface, because the very same interface can be used for different applications with totally different needs.
The use of interfaces engourages the use of inheritance.
One noticable thing about interfaces, the centerpiece concept of COM, is that once you've chosen an interface, or defined one, you will NEVER EVER change it. which provides for a mechanism to be backwards compatibility. (see msword 7-msword 8).
There's far more to it than this, but remember this:
Think COM, think interface.
Recommended reading: Inside COM and Inside Ole (Microsoft press, I think)
0
 
stinger_60284Author Commented:
Thanks Thaddy's for the explanation.
I'll appreciate it so much.
:)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now