Fast Binding Option for Batch Write/Modify Operations

When you call GetObject, ADsGetObject, ADsOpenObject, or IADsOpenDSObject::OpenDSObject, ADSI creates a COM object that represents the specified directory object. Normally, ADSI first retrieves the objectClass property so that ADSI can expose the COM interfaces that are appropriate for that class of object. For example, a user object would expose the IADsUser interface in addition to the base ADSI interfaces supported for all objects (such as IADs, IDirectorySearch, IDirectoryObject, and so on).

For a single operation, this should have no effect on performance. However, if you are doing batch operations that require hundreds or thousands of bindings over a slow connection and those operations are write methods in the base ADSI interfaces (such as IADs::Put and IDirectoryObject::SetObjectAttributes), you may want to trade off full object support (that is, the object-specific interfaces such as IADsUser on user objects) for faster binding. To do this, use the ADS_FAST_BIND flag for ADsOpenObject and IADsOpenDSObject::OpenDSObject.

The ADS_FAST_BIND flag has the following effects:

• The bind operation uses ADsOpenObject or IADsOpenDSObject::OpenDSObject and goes to the directory server once instead of twice. ADSI does not read objectClass and, therefore, exposes only the base ADSI interfaces for the object.
• Only the following ADSI interfaces are supported on the ADSI COM object:

  IADs

  IADsContainer

  IDirectoryObject

  IDirectorySearch

  IADsPropertyList

  IADsObjectOptions

  ISupportErrorInfo

  IADsDeleteOps

• If you use IADsContainer::GetObject to bind to child objects, the object returned will also have ADS_FAST_BIND characteristics.
• No existence check for the object specified by the binding string. This means that subsequent method calls will fail if the object does not exist. Therefore, you should use the ADS_FAST_BIND option when you know the object already exists (for example, directly after performing a query that returned the distinguished names of the objects you want to bind to).
• ADSI extensions are exposed for objects of class top. Therefore, only the extensions for the base ADSI interfaces listed above are exposed.