Filesystemwatch er-- Realtime or not?

[RMB]

I am using the filesystemwatch er to track the movement of files from folder
to folder. I am tracking how long it takes for each file to get from point A
to point B. I have been able to do this, but would like to know if the
filesystemwatch er signals in realtime? I also noticed when the file activity
gets heavy the file system watcher does not signal for some files.

Thanks

[Markus]

> I also noticed when the file activity gets heavy the file system

watcher does not signal for some files.

to your second concern of heavy file-changes, please read the
documentation of the FileSystemWatch er carefully (in the .NET Framework
documentation):

"The Windows operating system notifies your component of file changes in
a buffer the created by the FileSystemWatch er. If there are many changes
in a short time, the buffer can overflow. This causes the component to
lose track of changes in the directory, and it will only provide blanket
notification. Increasing the size of the buffer with the
InternalBufferS ize property is expensive, as it comes from non-paged
memory that cannot be swapped out to disk, so keep the buffer as small
yet large enough to not miss any file change events. To avoid a buffer
overflow, use the NotifyFilter, and IncludeSubdirec tories properties so
you can filter out unwanted change notifications."

hth
Markus

[RMB]

Thank you Markus. I will experiment with the buffer size, as I am already
using the NotifyFilter with a single filter, and have set
IncludeSubdirec tories to false.

"Markus" wrote:

I also noticed when the file activity gets heavy the file system
watcher does not signal for some files.

to your second concern of heavy file-changes, please read the
documentation of the FileSystemWatch er carefully (in the .NET Framework
documentation):

"The Windows operating system notifies your component of file changes in
a buffer the created by the FileSystemWatch er. If there are many changes
in a short time, the buffer can overflow. This causes the component to
lose track of changes in the directory, and it will only provide blanket
notification. Increasing the size of the buffer with the
InternalBufferS ize property is expensive, as it comes from non-paged
memory that cannot be swapped out to disk, so keep the buffer as small
yet large enough to not miss any file change events. To avoid a buffer
overflow, use the NotifyFilter, and IncludeSubdirec tories properties so
you can filter out unwanted change notifications."

hth
Markus