Hello Graham,
Unfortunately in this instance 200mS is a problem. The client is performing a LIST every 3 seconds on the server. There may be 300-400 files in the list. All of a sudden the server flags every file as changed and the client has to download every file to see if the change is valid. So now 200mS per RETR accumulates to a significant time.
I don't know how far you can control both client and server side, but if you can change server side, probably it would be much better to design a specific server program instead of using FTP protocol.
FTP protocol is slow by design (design of the protocol, not design of ICS). There are two connections: one for control and one for data. Each file transfert needs a new data connection and this takes time to setup and close properly.
More, I understand you are doing a polling which is both slow and imposte an important load on the server.
I suggest you design a simple server which would use Windows API to be notified for file changes in the folder your are monitoring, send the notification to the client which would download the files using the same channel as the control channel, or even use multiple channels to download several files at once.
Regards, -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
