At 15.45 22/07/99 +0200, Simon Hausmann wrote:
>On Thu, 22 Jul 1999, Pietro Iglio wrote:
>
>> I would like to discuss the current implemention of KRegistry.
>> 
>> KRegistry acts like a "in memory" database of mimetypes and .desktop files.
>> It can be used to access information about a mimetype/desktop file (icon,
>> comment, etc.) without parsing the corresponding configuration file.
>> 
>> Currently, the whole registry is saved in a binary format under
>> ~/.kde/share/config/kregistry and its completely loaded in memory.
>> 
>> The limit of this approach is memory consumption, expecially if you have
>> a large number of applications installed.
>
>Not if it is loaded only one single time, in kded :-)

What about performance? Is it possible to use kded as a daemon from
applications that require fast access to the provided information, such
as konqueror and kpanel?

Are you sure that a remote call for each file in a directory isn't too
slow?

-- Pietro