Readonly
IDA unique identifier for this request context
Readonly
blockingNumber of active blocking transactions associated with this context
This gives out a weak pointer to the push cache. The nsIRequestContext implementation owns the cache and will destroy it when overwritten or when the context ends.
Optional
aInstancePtr: objectA run time mechanism for interface discovery.
NS_OK if the interface is supported by the associated instance, NS_NOINTERFACE if it is not.
aInstancePtr must not be null.
[in] A requested interface IID
[out] A pointer to an interface pointer to receive the result.
Called when the request is sitting in the tail queue but has been canceled before untailing. This just removes the request from the queue so that it is not notified on untail and not referenced.
If the request context is in tail-blocked state, the callback is queued and result is true. The callback will be notified about tail-unblocking or when the request context is canceled.
Generated using TypeDoc
The nsIRequestContext is used to maintain state about connections that are in some way associated with each other (often by being part of the same load group) and how they interact with blocking items like HEAD css/js loads.
This used to be known as nsILoadGroupConnectionInfo and nsISchedulingContext.