dcop auto-overuse

[Josef Weidendorfer]

On Wednesday 10 December 2003 16:18, Waldo Bastian wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wed December 10 2003 15:44, Josef Weidendorfer wrote:
> > Actually, starting a small server like dcopserver can't be the actual
> > problem. Instead of a standalone "konsole", "dcopserver; konsole" gives a
> > huge speedup. A delayed startup as with
> > 	(dcopserver; konsole) & (sleep 5; kdeinit)
> > gives you all the servers in the background.
> > Why can't this delaying be the default (used in a non-KDE szenario) ?
>
> You must be able to guarantee that konsole will not try to access
> klauncher, kded, kdeinit or ksycoca during the first 5 seconds and that it
> doesn't need kconf_update to update its settings before it uses them.

Is there a possibility to tackle these items for KDE 3.3?

If there is an explicit communication request from the app (for klauncher, 
kded, kdeinit), it should be possible to start these on demand via 
dcopserver. Isn't there already a similar mechanism implemented?

ksycoca shouldn't be any problem, as with a new installed app/component 
registered 5 secs. after program start, there will be a notification, no?

Can't kconf_update be triggered directly by the application?

Josef