COM / OLE / ActiveX / IDispatch confusion -
I can not wrap my head around the difference in these words.
COM and ActiveX are synonyms?
Is the Active X object only a comma object that exposes the IDISpatch?
IDIPPatch is mentioned without any COM reference in many old MSDN pages. Does it have a different history, and whether it was introduced under the 'COM' umbrella in its life cycle?
What is fit in wet ki? Is MFC Naming and Normal in its MSDN - Its Legacy?
Gives some insight, but not much. I could not find a more deep reference.
Some quotes were found:
One more thing you can do Will find that it was a field trip day with vocabulary in marketing. Instead of helping to promote understanding, you will promote this secret in most cases. ... OLE, Active X, Remoteable Object - which means this week? ...
Com evolved to solve a specific problem - allowing a word processor to exit the word processor without having to allow the user to edit the spreadsheet in a single letter. This solution is called OLE .... However, with the second release of OLE (OLE 2), its creator has further highlighted the basic functionality of OLE to modify OLE32.DLL so that its API is used by anybody The application can also be used to achieve the other's functionality. This API, which has not been changed more than the 1993, is considered a COM API ...
Once the COM API was exposed, Microsoft used it to use it , Which allows sophisticated controls for the OFL control (eg, buttons, which plays music, visual box, Visual C ++). Accessible for Visual Basic Applications This technique was ultimately used by your web browser to download and use a control. At this point, the name changed to ActiveX control or just plain ActiveX purely for marketing reasons. Although you can package any functionality in an ActiveX control, its specifications are specific to supporting its user interface control.
I'm still curious about the last sentence - should COM object satisfy some additional requirements to be eligible as an ActiveX control? - But it's enough to go.
Thank you for your reply!
Comments
Post a Comment