config option for KDirWatch method

Andreas Pakulat apaku at
Wed Aug 8 08:35:17 BST 2007

On 08.08.07 08:02:53, Jos van den Oever wrote:
> 2007/8/6, Andreas Pakulat <apaku at>:
> > On 06.08.07 13:33:07, Matthew Woehlke wrote:
> > > Andreas Pakulat wrote:
> > > >On 06.08.07 10:45:48, Matthew Woehlke wrote:
> > > >>Andreas Pakulat wrote:
> > > >>>+  KConfig config("kdeglobals");
> > > >>Any reason you do not use KGlobal::config()?
> > > >Well, I understood that as if KGlobal::config() would return me
> > > >kdeveloprc when used in kdevelop and katerc when used in kate.
> > >
> > > Right, but I'm going to go out on a limb here and guess that you get the
> > > system-wide settings unless the app has overridden them (which I would further
> > > suggest is The Right Thing To Do anyway). At least, I really hope that's the
> > > way it works, or else all of KGlobalSettings is horribly broken :-).
> >
> > Right, I never questioned that. However having different monitoring
> > methods for each app doesn't make that much sense IMHO.
> >
> > OTOH KDirWatcher already does use that for the polling interval, so in
> > theory you could have different polling intervals for each app.
> Do we leave room for later on switching to central daemon for get file
> change notifications?

As far as I can see: yes, the public API is clean enough for that.

> Inotify has a limit on the number of directories
> it can watch and is generally inefficient.

Well, for me fam is generally inefficient as well and polling surely is
no proper solution, so which one should I choose ;)

> This means that when many apps watch the filesystem for changes, this
> will become expensive.  Also polling is expensive and you would like
> to have 1 pollinground for all apps. Strigi will e.g. be watching many
> if not all files in someones home directory. A dbus daemon sending
> signals might be a solution here.

I guess global statics created in a shared library like kio are not
shared among processes right? (If they were we'd already have that
central daemon)


You are confused; but this is your normal state.

More information about the kde-core-devel mailing list