hey Remy Lebeau indy FTP Server question :-)

[snorkel]

Remy,
I sent you a private message about adding some events for the Indy FTP server component.
i.e. OnRetreiveFileDone and OnStoreFileDone.

[Thaddy]

I can't see any use for it. Can you add a simple example what you mean? I think you are missing something about the current functionality.

[snorkel]

there are of use if you are building a Managed FTPS/FTP system and you want to do something to the files after they are fully received/stored by the server.
For example:   have a sqlite database with rules based on Unix style pattern matching and then move the files based on stored destinations for those files, or maybe PGP decrypt the files automatically, do a Unix to Windows i.e. LF to CRLF conversion of the file, the list goes on and on.

It's just super nice having the events part of the server component.  Remy suggested doing a new inherited tfilestream object with a custom destroy event and that would probably work. 
But to me it just makes sense to have those two events fire when a file is Sent or Received :-)

I Implemented the events in my copy of Indy almost two years ago and the server has been in production for about 1.5 years and we transfer around 1k files per day and when a file is received I have a I/O completion port queue that does the processing based on the file pattern found in the sqlite database.  No issues with the events ever.
There are natural companions to the OnStoreFile and OnRetreiveFile events.

[snorkel]

Here is the event header for the OnStoreFileDone:

procedure TFTPDataMod.FTP_ServerStoreFileDone(ASender: TIdFTPServerContext;const AFileName: TIdFTPFileName;AFileSize:int64);

No need to create a custom tfilestream object and destructor, which of course would work just fine as well.   

At the time when I created the application it just seemed like a natural addition to the server component.

[snorkel]

I got it working the way Remy recommended using a custom tfilestream and destructor.
Though I think the events is cleaner.