bastian at kde.org
Thu Jun 26 15:25:21 BST 2003
-----BEGIN PGP SIGNED MESSAGE-----
On Thursday 26 June 2003 15:13, Ian Reinhart Geiser wrote:
> Really KConfigBase should be avoided so we can continue to clean up the API
> pre KDE 4.0. Currently the design ensures that we cannot have multiple
> backends, and that its VERY VERY hard to keep multiple instances of
> applications prefs in sync effectively.
That's a missing feature, yes. But I don't think the design prohibits
> Lucky due to waldo's awesome speed
> hacks we dont notice this on the INI backend, but on my SQL backend I was
> able to push my postgres server into a frenzy as it requerried the server
> about 49 times in konqis start up :) (*note* this is because of
> braindamages in how we do our standard dirs, and local stuff, not
> neccicarily kconfig. If i hack my env down, i can get konqi startup to
> only reparse KConfig files about 27-30 times. also when i say reparse, i
> mean it calls the reparse config of an individual file. afaik we only call
> reparse config everytime any stddir or resource is added... the problem is
> the complexity grows as you add more files.)
> LDAP was even worse, but that was because I made the mistake of doing each
> key as an entry and not one file as an entry.
At the time KConfig was designed the idea was that one could plugin other
(e.g; SQL/LDAP) backends directly into KConfig. Personally I don't think that
this is the way to go (too slow because too much roundtrip delay) and that
the correct solution is to have a seperate sync-daemon that fetches, syncs
and re-uploads (config-) files to the server and that applications basically
keeps using the existing INI-file backend.
Form there you could tweak things a little and instead of using the INI
backend, write a backend that communicates directly with the sync-daemon, but
I doubt that would gain you much. Such approach would be awefully close to
GNOME's GConf btw.
Can you post your stats on the files that get parsed during konqy startup?
bastian at kde.org -=|[ SuSE, The Linux Desktop Experts ]|=- bastian at suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----
More information about the kde-core-devel