On Thu, Nov 12, 2009 at 21:28, Peter Kasting <pkast...@google.com> wrote:
> On Thu, Nov 12, 2009 at 12:13 PM, John Abd-El-Malek <j...@chromium.org>wrote:
>
>> per our chat on irc, I think if a new privacy blacklist is added while
>> running, it should be loaded on the file thread, and when it's available the
>> IO thread should be updated. The user won't have expectations or know how
>> already pending requests are scheduled, and won't be loading a blacklist and
>> within a 100ms loading a page.
>>
>
> Well, if somebody uses these to write an adblocker that auto-updates its
> blacklists at frequent intervals, the last clause might be false. But it
> seems like loading the new list on the file thread and then pinging the IO
> thread is still the right thing to do then.
>
Just to clarify: a blacklist is an integral part of an extension, and must
be declared in its manifest. Updating a blacklist means updating the
extension.
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
