The server creates and manages COM Objects Based on Customer requests. A customer (usually an application) requests to create a COM Object and manipulate the COM object through the interface of the COM object. In essence, COM is still the client server mode. It provides standard interfaces for accessing core functions of COM objects and a set of API functions in the form of a COM Library (ole32.dll and oleaut32.dll, these API functions are used to create and manage COM objects. Com is both a standard and an implementation. In this way, even if the COM object is created by different programming languages and runs in different process spaces and different operating system platforms, these objects can communicate with each other. The question is, how do these component objects coexist with applications and other component objects and communicate and interact with each other? So what should I do? Standards, allowing these component objects to work in a unified standard manner.Ĭom is a binary specification and has nothing to do with source code. The so-called component object is actually a predefined service or interface that can complete certain functions. People always hope to "Assemble" applications as they build blocks, and component objects act as building blocks. Software reuse is the goal pursued by the industry.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |