RE: Strategy for FTP transfers

>So, my main questions are:
>
>  - how do you handle security (special FTP libs, users etc.) ?
If the far end is accessing YOUR system, then create a special library and
user profile that allows access to that library only.

>  - checking of successful transfers (logging)
Scott Klement has an open source API that might help:
http://klement.dstorm.net/ftpapi/  

>  - unexpected downtime of remote systems
This must be designed into your "push" application.  Usually, a simple DB
file containing a list of files that haven't been sent yet will work OK.
Try sending the first file on the list; if it fails, wait a predetermined
time and try again.  If it succeeds, delete the record from the "queue" and
send the next file.

>  - who initiates the transfer..
This depends entirely on your "trading partner."

Buck Calabro
Commsoft; Albany, NY
"Love truth but pardon error"
  -- Voltaire
Visit the Midrange archives at http://www.midrange.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---