New file system monitoring component

[pyscripter 828]

Whilst there are many Delphi components for detecting changes to file system folders they suffer from serious limitations:

• typically they only allow you to monitor a single folder
• they do not support the monitoring of specific files
• they rely on the FindFirstChangeNotification API which gives no information about what has changed, requiring an inefficient search.

 

I have created a new file system monitoring library that addresses the above limitations.

 

Features:

• Easy to use, but also suitable for heavy duty monitoring
• Single unit with no external dependencies
• Allows monitoring folders and/or specific files
• Uses the ReadDirectoryChangesW API which provides information about what exactly was changed
• A single instance of the component can handle the monitoring of many folders and/or files
• Uses an I/O completion port for efficient handling of large numbers of requests
• A single thread handles all requests
• A different notification handler can be specified for each request

• You can have multiple handlers for each folder or file

• When you monitor folders you can specify whether you want to also monitor subfolders

 

Installation:

You do not need to install the library. Just download or clone the repo and add the source subdirectory to the Library path.

 

Usage:

procedure TForm1.FormCreate(Sender: TObject);
begin
  // Create the IFileSystemMonitor interface
  FFileSystemMonitor := CreateFileSystemMonitor;
  // Monitor a directory
  FFileSystemMonitor.AddDirectory(TPath.GetTempPath, False, HandleChange);
  // Also monitor a specific file
  FFileSystemMonitor.AddFile('pathtoyourfile',  HandleChange);
end;

procedure TForm1.HandleChange(Sender: TObject; const Path: string;
  ChangeType: TFileChangeType);
begin
  with lvEventList.Items.Add do
  begin
    Caption := GetEnumName(TypeInfo(TFileChangeType), Integer(ChangeType));
    SubItems.Add(Path);
  end;
end;

To stop monitoring a specific file or folder you use the following methods:

    function RemoveDirectory(const Directory: string; OnChange: TMonitorChangeHandler): Boolean;
    function RemoveFile(const FilePath: string; OnChange: TMonitorChangeHandler): Boolean;

 

Edited Tuesday at 09:22 PM by pyscripter

[Tommi Prami 157]

Very nice.  Way better than constant polling for sure.

I think I have no use for this now, but have to think about it, maybe I can think of something.

In previous live used FindFirstChangeNotification  API, did not knoew that there is other API for this.

-Tee-

Edited Wednesday at 04:23 AM by Tommi Prami
typo

[Dave Novo 57]

Thanks for all the amazing work you do and contribute to the community!

[mjustin 31]

Sorry for asking, but is polling still necessary if the monitoring application (which uses IFileSystemMonitor) was not running for a while, and during that time changes happened?

Or does IFileSystemMonitor provide ways to detect changes which happened while it was "absent"?

[M.e.l 1]

Hi,

 

It looks simple and good.

Does it work across network or VPN ?

i.e. can a server directory be monitored from an app running your monitoring class on a client PC, connected to the server through network ?

 

Mel

 

[Anders Melander 2065]

38 minutes ago, M.e.l said:

Does it work across network or VPN ?

i.e. can a server directory be monitored from an app running your monitoring class on a client PC, connected to the server through network ?

VPN is just transport layer encryption and is not relevant.

 

The documentation for ReadDirectoryChangesW answers your other question:

Quote

If the network redirector or the target file system does not support this operation, the function fails with ERROR_INVALID_FUNCTION.

Quote

In Windows 8 and Windows Server 2012, this function is supported by the following technologies.

Technology	Supported
Server Message Block (SMB) 3.0 protocol	Yes
SMB 3.0 Transparent Failover (TFO)	Yes
SMB 3.0 with Scale-out File Shares (SO)	Yes
Cluster Shared Volume File System (CsvFS)	Yes
Resilient File System (ReFS)	Yes

 

 

[pyscripter 828]

@mjustin

Have a look at the source code.  https://github.com/pyscripter/FileSystemMonitor/blob/2dd27a0570ae2f839acb9de3bf67bb2247893784/Source/FileSystemMonitor.pas#L415C16-L415C41

All the thread does is wait on the I/O complection port using GetQueuedCompletionStatus.  This function blocks until a change happens. The only polling that takes place is to check every 5 seconds, for deletion/rename of the monitored directories themselves, which are not reported by ReadDirectoryChanges.  Folders can be attached to/detached from the completion port at any time, without any problem.

[Anders Melander 2065]

41 minutes ago, pyscripter said:

deletion/rename of the monitored directories themselves, which are not reported by ReadDirectoryChanges.

...unless you also monitor the parent directory. Maybe make the polling optional?

[pyscripter 828]

10 hours ago, Anders Melander said:

...unless you also monitor the parent directory.

You will still have the same issue if the parent directory (or the parent of the parent...) gets deleted or renamed.  Even if not,  you may be getting many more notifications than you need.  Also you would have to watch subfolders, which you may not want. 

 

It is not worth it. Checking every x seconds whether the monitored directories still exist, is a tiny overhead.

Edited 19 hours ago by pyscripter

[Ian Branch 141]

Users may find this useful.

Found a Bug.  Corrected.

 

gllFileSystemMonitor.rar

Edited 10 hours ago by Ian Branch

[Tommi Prami 157]

7 hours ago, Ian Branch said:

Users may find this useful.

Found a Bug.  Corrected.

 

gllFileSystemMonitor.rar

Could you make Pull Request?

PS. Recently there has been reports of malicius .RAR-files. So maybe better avoid them,  when sending files into public forums. 

[Ian Branch 141]

 

29 minutes ago, Tommi Prami said:

Could you make Pull Request?

How do i do that?  It is on my PC.

[Ian Branch 141]

P.S.  I just found another Bug. 😞  Nothing significant.  Working on it.

The current upload should work fine for most cases.

Edited 9 hours ago by Ian Branch

[Tommi Prami 157]

19 hours ago, pyscripter said:

It is not worth it. Checking every x seconds whether the monitored directories still exist, is a tiny overhead.

This depends. 


Should measure this some day... But we have soemthing Fishy in our VPN and/or Serever(s). If there is any ongoing copy etc longer lasting file operation to/from  the server, all file other operations takes ages, It used to be even worse than  now. All clics with File Exoplorer, in that situation, takes more than Second. It really seems to be fluctuating a lot also. But for sure File Explorer does more than just checks is the file there or not.

So I was tinking that wait time would be something like Mintime (Like 5sec) plus 20-50x to what check operation too last time- Or something like that. Should keep that per root (Like N:\ orm \\CommonFiles\ etc)

Just my 0.02€, might work, maybe not...

-Tee-

[Tommi Prami 157]

15 minutes ago, Ian Branch said:

 

How do i do that?  It is on my PC.

Fork the repository from the GitHUB, make changes and make pull request.

Details really depends will you use commndline tool(s) or some GUI tool.  I mainly use Theirs GitHUB Desktop https://desktop.github.com/download/

It is very simple on  most operations, and this is why I kind of like it.

-tee-

[Ian Branch 141]

As I said, it is on my PC, not on GitHub.

[Ian Branch 141]

Minor Bug fixed:

 

gllFileSystemMonitor.rar

[Anders Melander 2065]

42 minutes ago, Ian Branch said:

As I said, it is on my PC, not on GitHub.

Maybe this would be a good occasion to learn Git then...

 

Here's a quick intro I made for someone else that wanted to contribute a change to Graphics32:

 

On Github

1. Create a Github account: https://github.com/signup
2. Fork the Graphics32 repository to your own Github account.
   
   This gives you a copy, on your own Github account, of the main repository where you can push your changes.

 

On your local system

1. Clone your own Graphics32 repository to your local system using a Git client.
   I recommend the Fork git client: https://git-fork.com/
2. Create a branch in your local repository.
3. Commit your changes to that branch.
4. Push the branch to your own Graphics32 repository.

 

On Github

1. Create a pull request on your Graphics32 repository.
   

2. Specify the master branch at the main Graphics32 repository as the target, and your branch at your repository as the source.
   

3. When Github notifies me that you have submitted a pull request I'll review the changes.
   Once I accept the pull request, the changes are merged into the branch you specified as the target branch.