See Also
 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
This interface accepts information on an asynchronous bind operation.
In This Section
- GetBindInfo
-
Provides information about how the bind operation should be handled when it is called by an asynchronous moniker
- GetPriority
-
Obtains the priority for the bind operation when it is called by an asynchronous moniker
- OnDataAvailable
-
Provides data to the client as it becomes available during asynchronous bind operations
- OnLowResource
-
Currently not implemented
- OnObjectAvailable
-
Passes the requested object interface pointer to the client
- OnProgress
-
Indicates the progress of the bind operation
- OnStartBinding
-
Notifies the client about the callback methods it is registered to receive. This notification is a response to the flags the client requested in the RegisterBindStatusCallbackfunction
- OnStopBinding
-
Indicates the end of the bind operation
Remarks
A client requesting an asynchronous bind operation must provide a notification object exposing the IBindStatusCallbackinterface. The asynchronous moniker provides information on the bind operation to the client by calling notification methods on the client's IBindStatusCallbackinterface. This interface also allows for the client to pass additional bind information to the moniker by calling the IBindStatusCallback::GetBindInfoand IBindStatusCallback::GetPrioritymethods after it receives a call from IMoniker::BindToObjector IMoniker::BindToStorage.
Only the last IBindStatusCallbackinterface that was registered will be called.
Requirements
| Header | urlmon.h, urlmon.idl |
| Library | urlmon.lib |
| Windows Embedded CE | Windows CE .NET 4.0 and later |
| Windows Mobile | Windows Mobile Version 5.0 and later |
See Also
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.