[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KConfig again
From:       Steffen Hansen <stefh () mip ! sdu ! dk>
Date:       1999-05-15 22:04:01
[Download RAW message or body]

On Sat, 15 May 1999 pbrown@redhat.com wrote:

> Mosfet and I were talking, and we made the hypothesis that most apps using
> a KConfig object to a few initial readEntry()s, and then they basically
> don't touch the KConfig object again until it is time to shut down (i.e.
> destroy the object / save changes).  This means that keeping KConfig
> entries around in RAM (cached) is rather a waste.  It would seem to make
> more sense to read it dynamically off the disk when needed.
> 
> Comments?

This was exactly that i thought when suggesting that you could try the
slower O(n^2) method where you iterate through the kconfig file and search
for the group/key the app asks for. 

Maybe the app should decide for itself if entries should be cached in RAM
(in a QMap).

greetings,
--------------
Steffen Hansen                              |
email: stefh@mip.sdu.dk, stefh@imada.sdu.dk,|  
       hansen@kde.org                       | ABC...VWXKZ :)
URL:   http://www.mip.sdu.dk/~stefh         | 

[prev in list] [next in list] [prev in thread] [next in thread]