| UID | title | description | helpviewer_keywords | old-location | tech.root | ms.assetid | ms.date | ms.keywords | req.header | req.include-header | req.target-type | req.target-min-winverclnt | req.target-min-winversvr | req.kmdf-ver | req.umdf-ver | req.ddi-compliance | req.unicode-ansi | req.idl | req.max-support | req.namespace | req.assembly | req.type-library | req.lib | req.dll | req.irql | targetos | req.typenames | req.redist | ms.custom | f1_keywords | dev_langs | topic_type | api_type | api_location | api_name | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NN:objidl.IInternalUnknown |
IInternalUnknown (objidl.h) |
The IInternalUnknown interface (objidl.h) is used exclusively in lightweight client-side handlers that require access to the internal interfaces on the proxy. |
|
com\iinternalunknown.htm |
com |
d2f4c8bc-80b9-4ba0-9f30-f0864144902b |
08/15/2022 |
IInternalUnknown, IInternalUnknown interface [COM], IInternalUnknown interface [COM],described, _com_iinternalunknown, com.iinternalunknown, objidlbase/IInternalUnknown |
objidl.h |
ObjIdl.h |
Windows |
Windows 2000 Professional [desktop apps only] |
Windows 2000 Server [desktop apps only] |
ObjIdl.idl |
Windows |
19H1 |
|
|
|
|
|
|
Used exclusively in lightweight client-side handlers that require access to some of the internal interfaces on the proxy.
The IInternalUnknown interface inherits from the IUnknown interface. IInternalUnknown also has these types of members:
Handlers that need access to some of the internal interfaces on the proxy manager have to go through the IInternalUnknown interface. This prevents the handlers from blindly delegating and exposing the aggregatee's internal interfaces outside of the aggregate. These interfaces include IClientSecurity and IMultiQI. If the handler wants to expose IClientSecurity or IMultiQI, the handler should implement these interfaces itself and delegate to the proxy manager's implementation of these interfaces when appropriate.
For the IClientSecurity interface, if the client tries to set the security on an interface that the handler has exposed, the handler should set the security on the underlying network interface proxy.
For the IMultiQI interface, the handler should fill in the interfaces it knows about and then forward the call to the proxy manager to fill in the rest of the interfaces.