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 enables downloading code to write data asynchronously to a structured storage byte array.
When the downloading code has new data available, it calls IFillLockBytes::FillAppendor IFillLockBytes::FillAtto write the data to the byte array.
An application attempting to access this data through calls to the ILockBytesinterface can do so even as the downloader continues to make calls to IFillLockBytes.
If the application attempts to access data that has not been downloaded through a call to IFillLockBytes, ILockBytesreturns a new error, E_PENDING.
When to Implement
You typically would not implement this interface.
A system developer that wants to provide asynchronous storage for a protocol other than HTTP might implement IFillLockBytesas part of the transport layer.
When to Use
You typically would not call this interface. Monikers or other downloading code that provide asynchronous storage use this interface to fill the byte array as data becomes available.
Methods in Vtable Order
IUnknown method | Description |
---|---|
Returns pointers to supported interfaces. |
|
Increments the reference count. |
|
Decrements the reference count. |
Method | Description |
---|---|
Writes a new block of bytes to end of byte array. |
|
Writes a new block of bytes to specified location in byte array. |
|
Sets expected size of byte array. |
|
Notifies byte array wrapper of successful or unsuccessful termination of download. |
Remarks
To determine whether the platform supports this interface, see Determining Supported COM APIs.
Requirements
Header | objidl.h, objidl.idl |
Library | ole32.lib, uuid.lib |
Windows Embedded CE | Windows CE 3.0 and later |
Windows Mobile | Windows Mobile Version 5.0 and later |