>> Before now I thought it would be easier to derive a class from >> nsHttpHandler and register it for the http protocol right after xpcom is >> initialized and all the modules are loaded and initialized. > > That would work as long as the protocol handler caching in nsIOService > doesn't bite you. >
Thanks, I noticed this cache and it looks like nsIOService fills up the cache upon requests are comming, so it looks like I'm safe with my approach until at least one request with http scheme is made before I register my new handler. Right? Probably the best place for installing the handler is callback triggered on the network-up event. I know tear-down event, probably something like network-up is implemented too. On the other hand, it looks like nsIProtocolProxyService is a better way and I'd prefer to use it instead of mybrandnewHttpHandler. Still checking nsIProtocolProxyService and around to see if it's useful in my case. Regards. _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
