On Thu, Nov 12, 2009 at 20:26, John Abd-El-Malek <j...@chromium.org> wrote:
> My question still stands: if this list is needed in order to process the
> first network request, why add extra complexity to RDH to make more things
> asynchronous, when either way any IO is basically blocked on the blacklist?
> You might as well load the list on the IO thread.
>
Indeed, that would simplify a lot of things. However, we may recompile the
blacklist when browser is running, for example when loading a new extension.
In that case, we probably don't want to stall the IO thread.
The difference is that when starting the browser, we don't have yet any
blacklist. We should definitely wait for the blacklists to load, because it
would be surprising for the user if the blacklist doesn't take effect for
some time after starting the browser.
When changing the blacklists when the browser is already running, it's more
complicated.
Nick, could you comment whether new network requests should be paused when a
blacklist is changing? (for example due to now extension being loaded)
Not waiting then would make things trivial. And anyway, "waiting" for
blacklists after the browser started is even more surprising, as some
request may already be started (it's not obvious what to do with them).
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
