Currently we don't start the request in ResourceDispatcherHost until the
user script is ready (or not needed). UserScriptListener handles that. We
also wait for SafeBrowsing, Plugins, etc. We're going to wait for
PrivacyBlacklists.
I was thinking about refactoring RDH so that it would be easy to pause
requests (or not start them) until something is ready. For some things we
can just pause requests (like SafeBrowsing), for some we can't even start a
request (like Privacy Blacklist, which can block sending the referrer, User
Agent, cookies, etc or just cancel the entire request).
How would you recommend doing that? I think I wouldn't switch all existing
things to it immediately (it's a complex piece of code). I'd probably start
with UserScriptListener just to try it, and then Privacy Blacklists. What do
you think?
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
