🚀 go-pugleaf

> [...] But I may be monitoring hundreds or thousands of files and to do a 
> file search in a path to see which
> file has changed is going to be too time consuming.

Hmm... I don't know if such techique exists...

I have some projects that monitors specified folder
(and subfolders) for changes, and then I look what
file(s) is(are) changed.

I haven't found any time-delay problems.

I hold the previous files state (file size or file attributes) in
INI file and then compare it with changed once.

I suppose that the notification module you have is a
class, so can you make a couple of notification objects
(not only one) which will decrese the number of files to
monitor?

The problem I had with *all* change notification classes
I found so far was that the event is trigered *multiple*
times for one event ?!...

In practise, that means, when I have to do something (when
the change arrises), my processing code is executed multiple
times for the same set of data.




-- 
Best regards,
Vladimir Stefanovic