On 29 Jul, Mark B. Elrod wrote:
> "register" themselves once upon startup. i have noticed that netscape
> avoids the overhead of loading shared objects at startup by placing
> registration info inside resources associated with the shared objects.
> While this allows them to load faster as the beginning it is a little
> obscure. i still think loading the plugins and sending them a
> registration message would be the best way to handle this and then
> unload the plugins until you need them. how should decoders determine if
> they handle a bitstream though? it sucks to have to use file
For now I think we should open the object and the ask it what it
supports. Later on we should cache that information to avoid doing it
each time -- instead we can just stat the file and check to make sure
the one we have the info for.
I would like to keep away from using resources to do this, since there
is no equivalent concept under UNIX.
--ruaok Freezerburn! All else is only icing. -- Soul Coughing
Robert Kaye -- [EMAIL PROTECTED] http://moon.eorbit.net/~robert
