Hello,

I read a lot about the .NET FileSystemWatcher.
E.g.
http://www.codeproject.com/KB/vb/AdvancedFileSystemWatcher.aspx
http://vbnotebookfor.net/2007/10/01/introduction-to-filesystemwatcher/

Can anybody tell me how much resources a FileSystemWatcher in waiting
state consumes?

I would exspect, as there seems not to be an active polling of a
special directory, but only a kind of waiting for getting informed
about an Event, there is nearly no rescource consuming on CPU or
memory...

Am i right?

Cipherwar

Reply via email to