Re: oaf async activation

[Maciej Stachowiak <mjs eazel com>]

Martin Baulig <martin home-of-linux org> writes:

> Mathieu Lacage <mathieu eazel com> writes:
> 
> > This is not a "tiny gain". Activating mozilla takes 5 to 10 seconds on my 
> > machine which is a PIII 700 MHz... The UI is blocked for almost 4 to 7 
> > seconds which is unaceptable.
> 
> Well, at the presentation in Erlangen I started the Mozilla component and
> it took between 30 seconds (with a working network connection) and 5 minutes
> (with a broken network connection) to start up and the network connection was
> very broken most of the times.
> 
> I don't know what Mozilla is doing all the time (maybe trying to resolve
> www.mozilla.org which obviously cannot work without a working name server),
> but this is simply too long.
> 

Those times are way too long for anything. If you can reproduce times
like that with recent code, please file a Nautilus bug report.

In any case, sucky slow to start components will always exist, no
matter how hard we try; I think it's only reasonable to let oaf
clients avoid blocking their UI in such a case.

 - Maciej