3.1.4.2 IWbemObjectSink Interface Server Details
The IWbemObjectSink interface MUST be implemented by the WMI client if the WMI client uses asynchronous method calls as specified in section 3.2.4.2.9. In this case, the WMI client acts as an IWbemObjectSink server. The WMI server acts as an IWbemObjectSink client and invokes the IWbemObjectSink methods to deliver the results (IWbemClassObjects, if any, and the status code) of the IWbemServices method for which this IWbemObjectSink is passed as a response handler.
If the WMI client calls the IWbemServices::QueryObjectSink method, the IWbemObjectSink interface MUST be implemented by the WMI server and MUST be returned to the client in the ppResponseHandler parameter, as specified in section 3.1.4.3.3. In this case, the WMI server acts as an IWbemObjectSink server. The WMI client acts as an IWbemObjectSink client and invokes the IWbemObjectSink methods to deliver the results, that is, IWbemClassObjects that represent the extrinsic events the client wants to deliver to the server.
Because this interface is implemented by the WMI client and the WMI server and called by both, the server in this section refers to the implementer of this interface and the client refers to the caller in a specific scenario.
The IWbemObjectSink interface is a DCOM Remote Protocol (as specified in [MS-DCOM]) interface. The interface MUST be uniquely identified by UUID {7c857801-7381-11cf-884d-00aa004b2e24}.
Methods in RPC Opnum Order
|
Method |
Description |
|---|---|
|
The server receives the IWbemClassObject interfaces, which are sent in an ObjectArray structure. These objects are the result of an IWbemServices asynchronous method call that was started with this sink as the response handler. Opnum: 3 |
|
|
The server receives either a completion status code or information about the progress of the operation that was started with this sink as the response handler. Opnum: 4 |