nsISupports
Last changed in Gecko 1.8 (Firefox 1.5 / Thunderbird 1.5 / SeaMonkey 1.0)void asyncOpenAt(in nsIStreamListener listener, in nsISupports ctxt, in unsigned long startPos, in nsIResumableEntityID entityID); Obsolete since Gecko 1.8 |
void resumeAt(in unsigned long long startPos, in ACString entityID); |
Attribute | Type | Description |
entityID | ACString | The entity id for this URI. Available after OnStartRequest. Read only. Exceptions thrown
|
Open this channel, and read starting at the specified offset.
The request given to the nsIStreamListener
will be QIable to nsIResumableInfo
.
void asyncOpenAt( in nsIStreamListener listener, in nsISupports ctxt, in unsigned long startPos, in nsIResumableEntityID entityID );
listener
ctxt
startPos
entityID
Prepare this channel for resuming. The request will not start until asyncOpen or open is called. Calling resumeAt
after open or asyncOpen has been called has undefined behaviour.
During OnStartRequest, this channel will have a status of NS_ERROR_NOT_RESUMABLE if the file cannot be resumed, for example because the server doesn't support this. This error may occur even if startPos is 0, so that the front end can warn the user.
Similarly, the status of this channel during OnStartRequest may be NS_ERROR_ENTITY_CHANGED, which indicates that the entity has changed, as indicated by a changed entityID
.
In both of these cases, no OnDataAvailable will be called, and OnStopRequest will immediately follow with the same status code.
void resumeAt( in unsigned long long startPos, in ACString entityID );
startPos
entityID