Hi, We also need to know which app is attempting to open a channel. AFAIK, it might be difficult to know the app information (app id) if we implement this event in SocketTransport. As a SocketTransport instance is not belong to a single app and can be reused by nsHttpChannels form various apps.
Patrick ----- Original Message ----- From: "Christian Biesinger" <[email protected]> To: "Jason Duell" <[email protected]> Cc: "Jonas Sicking" <[email protected]>, [email protected], "Patrick Wang" <[email protected]>, "Boris Zbarsky" <[email protected]> Sent: 2012年8月11日 星期六 14:05:51 Subject: Re: Add new "network channel about to connect" event to nsIObserverService? I can't look at bugzilla right now, but I think you're better off to add this to the socket transport service. Just because channels can be implemented by lots of things but there's only one socket transport service, that way you're guaranteed to catch all network activity. Written on my phone will jelly bean voice recognition. Results were dubious. On Aug 10, 2012 12:49 PM, "Jason Duell" < [email protected] > wrote: In https://bugzilla.mozilla.org/ show_bug.cgi?id=780087 we'll be blocking B2G app's traffic if they exceed a quota, and/or only allow it if the phone is in a wifi network, etc. Honza came up with the idea of adding a CSP policy to do this monitoring, but sicking comments on IRC that "putting it in the CSP code sounds like a scary hack though given that it's not CSP code at all". So perhaps CSP is a bad place for it. We could use http-on-modify-request, but that only fires for HTTP requests. I'm currently thinking we might want to add a new nsIObserverService notification that's issued for "necko channel for app AppID about to connect on network interface FOO". How does that sound? Am I missing some other clever way of doing this? Jason _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
