Nickolay Ponomarev wrote:
You probably know it, but for the sake of people who'll find this in
Google, the stream listener is only required to implement the first
three methods - from nsIStreamListener and nsIRequestObserver (+ QI).
The rest can be implemented by another object, which is used to set
the channel's notificationCallbacks property. I don't think necko
attempts to get those from the stream listener.
Indeed, stream listeners are only ever used for nsIRequestObserver and
nsIStreamListener.
The others are indeed only used via the notification callbacks. You can
also leave that property null if you want. onStatus/onProgress (via
nsIProgressEventSink) are probably not often needed by extensions...
Why have both onChannelRedirect and onRedirect? Do you want to be
compatible with pre-1.8 Gecko?
-christian
--
All the world's a stage,
And all the men and women merely players:
They have their exits and their entrances;
And one man in his time plays many parts, [...] --W. Shakespeare
_______________________________________________
dev-tech-xpcom mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-xpcom
