It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it . ContentsThe article may be deleted if this message remains in place for seven days, i.e., after 20:12, 24 March 2025 (UTC). Find sources: "IUnknown" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{ subst:proposed deletion notify |IUnknown|concern=Fails [[WP:NSOFT]]}} ~~~~ |
In computer programming, the IUnknown interface is the fundamental interface in the Component Object Model (COM). The COM specification [1] mandates that COM objects must implement this interface. Furthermore, every other COM interface must be derived from IUnknown. IUnknown exposes two essential features of all COM objects: object lifetime management through reference counting, and access to object functionality through other interfaces.
An IUnknown (or IUnknown-derived) interface consists of a pointer to a virtual method table that contains a list of pointers to the functions that implement the functions declared in the interface, in the order that they are declared in the interface. The in-process invocation call overhead is therefore identical to virtual method calls in C++. [2]
The IUnknown interface exposes three methods: QueryInterface, AddRef, and Release: [3]
QueryInterface allows the caller to retrieve references to the interfaces that the component implements. It is similar to dynamic_cast <> in C++ or casts in Java and C#. Specifically, it is used to obtain a pointer to another interface, given a GUID that uniquely identifies that interface (commonly known as an interface ID , or IID). If the COM object does not implement that interface, an E_NOINTERFACE error is returned instead.AddRef is used to increment the reference count when a new client is acquiring the object. It returns the new reference count.Release is used to decrement the reference count when clients have finished using the object. It returns the new reference count. The object will delete itself during release when the reference-count reaches zero, which means that the caller must never use an interface after calling Release.interfaceIUnknown{virtualHRESULTQueryInterface(REFIIDriid,void**ppvObject)=0;virtualULONGAddRef()=0;virtualULONGRelease()=0;};The IUnknown interface ID is defined as a GUID with the value of {00000000-0000-0000-C000-000000000046}.
A COM component's interfaces are required to exhibit the reflexive, symmetric, and transitive properties. The reflexive property refers to the ability for the QueryInterface call on a given interface with the interface's ID to return the same instance of the interface. The symmetric property requires that when interface B is retrieved from interface A via QueryInterface, interface A is retrievable from interface B as well. The transitive property requires that if interface B is obtainable from interface A and interface C is obtainable from interface B, then interface C should be retrievable from interface A.