KDirWatch emitting dirty signal many times for one change

[Josef Weidendorfer]

On Tuesday 13 April 2004 22:30, Sébastien Laoût wrote:
> > Currently, KDirWatch can not notify you about file renaming because it
> > simply has no signal to notify renamings. Perhaps it's the best to add
> > rename notification to KDirWatch, especially since DNOTIFY and FAM indeed
> > seem to support it (for KDE 3.3, we could add a method returning a
> > RenameNotifier helper object that can emit this signal).
>
> OK.
> Would be fine.
> Seem quite complicated (why do not simple emit a fileRenamed() instead
> of create new objects and... thinks I don't understand).

Binary compatibility: Adding virtual methods (like signals) to library classes 
is not allowed in KDE 3.x...

> > For meta information, you should use extended file attributes instead
> > (KDE has already an interface for this (?)).
>
> Extended file attributes ?
> Never read this !
> Is it well spreaded ?
> Is it the thing that is in the new Linux 2.6 ? To manage rights for
> instance ? Or on some FileSystem only ?

I don't think that it's a 2.6 issue. The file system has to support it. I 
don't know what's the status here. Does anybody know if XFS/ext2/ext3 on 
current Suse/Fedora/Redhat already support them ??

> Is this supported by "extended file attributes" ?

Don't know. But for sure an extended attribute can store the file name of some 
XML file where all your meta information is stored or some index into a meta 
information table inside of your app. The important thing here is that 
renaming doesn't change the extended attribute.

> Hum... OK.
> How does Windows handle this issue ?
> Is this working under Windows ?
> I think yes : it's Windows (only one API, OS and GUI layers are
> mixed...).
> Is anyone tried ?

No idea.

Josef