Bewerken

Delen via

Making a Semisynchronous Call with C++

  • Artikel

Semisynchronous calls are the recommended means to call WMI methods, such as IWbemServices::ExecMethod and provider methods, such as the Chkdsk Method of the Win32_LogicalDisk Class.

One disadvantage of synchronous processing is that the caller thread is blocked until the call completes. The blockage can cause a delay in processing time. In contrast, an asynchronous call must implement SWbemSink in script. In C++, asynchronous code must implement the IWbemObjectSink interface, use multiple threads, and control the flow of information back to the caller. Large result sets from queries, for example, can take a considerable amount of time to deliver and forces the caller to spend significant system resources to handle the delivery.

Semisynchronous processing solves both the thread blockage and uncontrolled delivery problems by polling a special status object that implements the IWbemCallResult interface. Through IWbemCallResult, you can improve the speed and efficiency of queries, enumerations, and event notifications.

The following procedure describes how to make a semisynchronous call with the IWbemServices interface.

To make a semisynchronous call with the IWbemServices interface

  1. Make your call as normal, but with the WBEM_FLAG_RETURN_IMMEDIATELY flag set in the IFlags parameter.

    You can combine WBEM_FLAG_RETURN_IMMEDIATELY with other flags that are valid for the specific method. For example, use the WBEM_FLAG_FORWARD_ONLY flag for all calls that return enumerators. Setting these flags in combination saves time and space, and improves responsiveness.

  2. Poll for your results.

    If you call a method that returns an enumerator, such as IWbemServices::CreateClassEnum or IWbemServices::ExecQuery, you can poll the enumerators with the IEnumWbemClassObject::Next or IEnumWbemClassObject::NextAsync methods. The IEnumWbemClassObject::NextAsync call is nonblocking and returns immediately. In the background, WMI begins to deliver the requested number of objects by calling IWbemObjectSink::Indicate. WMI then stops and waits for another NextAsync call.

    If you call a method that does not return an enumerator, such as IWbemServices::GetObject, you must set the ppCallResult parameter to a valid pointer. Use the IWbemCallResult::GetCallStatus on the returned pointer to retrieve WBEM_S_NO_ERROR.

  3. Finish your call.

    For a call that returns an enumerator, WMI calls IWbemObjectSink::SetStatus to report the completion of the operation. If you do not need the entire result, release the enumerator by calling the IEnumWbemClassObject::Release method. Calling Release results in WMI canceling the delivery of all objects that remain.

    For a call that does not use an enumerator, retrieve the GetCallStatus object through the plStatus parameter of your method.

The C++ code example in this topic requires the following #include statements to compile correctly.

#include <comdef.h>
#include <wbemidl.h>

The following code example shows how to make a semisynchronous call to GetObject.

void GetObjSemiSync(IWbemServices *pSvc)
{

    IWbemCallResult *pCallRes = 0;
    IWbemClassObject *pObj = 0;
    
    HRESULT hRes = pSvc->GetObject(_bstr_t(L"MyClass=\"AAA\""), 0,
        0, 0, &pCallRes
        );
        
    if (hRes || pCallRes == 0)
        return;
        
    while (true)
    {
        LONG lStatus = 0;
        HRESULT hRes = pCallRes->GetCallStatus(5000, &lStatus);
        if ( hRes == WBEM_S_NO_ERROR || hRes != WBEM_S_TIMEDOUT )
            break;

        // Do another task
    }

    hRes = pCallRes->GetResultObject(5000, &pObj);
    if (hRes)
    {
        pCallRes->Release();
        return;
    }

    pCallRes->Release();

    // Use the object.

    // ...

    // Release it.
    // ===========
        
    pObj->Release();    // Release objects not owned.            
  
}

Calling a Method