It appears that Mozilla (maybe for similar reasons) caches this info
across browser runs and relies on the file mtime to see when its cache
has expired, much to some users' dismay:
https://bugzilla.mozilla.org/show_bug.cgi?id=125469
Or at least they did in 2002. ;)
yea, they definitely
I was just reminded of this thread. I'm not sure if it was
premeditated, but having the mime-types be a function
(NP_GetMIMEDescription) is actually important for a specific Linux
use-case. nspluginwrapper is a single plugin that proxies access to
other plugins (for example, 64bit - 32bit). It
On Tue, Jan 27, 2009 at 6:38 PM, Evan Martin e...@chromium.org wrote:
I'd been sending this sort of stuff to Dean and John but maybe other
people will find it interesting.
Plugin loading works in two phases:
- at startup, we scan the plugin directories for metadata, like plugin
names and
Wow. It sucks that we'll need to load plugins in the main browser process.
That gives plugins a nice opportunity to hose the browser. Oh well :-( If
we really wanted to, I suppose we could have a plugin scanner process, but
that seems unfortunately heavyweight.
-Darin
On Tue, Jan 27, 2009
One of my goals with the out of process worker code is it to make it easier
to have many different types of child processes. Perhaps it makes sense to
have the linux port do this stuff in a child process once that code is
ready.
On Tue, Jan 27, 2009 at 10:49 PM, Darin Fisher da...@chromium.org
