Scott MacGregor wrote:
> The uri loader requires an OnStartRequest in order to find an
> appropriate consumer for the content. Until an OnStart is issued, the
> uriloader is the only one receiving nsIStreamListener notifications.
> So if you try to bypass the OnStart and call using a new OnFailure
> method or just the OnStopRequest your operation will fall on the
> floor. The uriloader will get the OnStop/OnFailure notification,
> notice that it doesn't have a consumer for the stream to forward these
> notifications to and will just stop processing things.
>
> So I'm not sure what we'd gain with bypassing OnStartRequest withouht
> over hauling the uriloader as well.
is the overhaul hard? I'm envisioning popping a bool check into onstart
and taking pathA in onstop() if onstart was never called, and pathB in
onstop() if it was?
Jud
