Lianja

Send an FTP NOOP (Keep-Alive)

Demonstrates the Chilkat Ftp2.Noop method, which sends the FTP NOOP command. It takes no arguments and succeeds only when the server returns a positive reply.

Background: NOOP asks the server to do nothing and simply reply, which makes it the standard keep-alive: sending one periodically resets the server's idle timer so a long-running job does not lose its control connection between transfers. Because it exercises a real request/reply round trip, a successful NOOP is also firmer evidence the connection is alive than CheckConnection.

Chilkat Lianja Downloads

Download Chilkat for Lianja

Lianja

llSuccess = .F.

//  Demonstrates the Ftp2.Noop method, which sends the FTP NOOP command.  It takes no arguments.
//  The server must return a positive reply for the method to succeed.

loFtp = createobject("CkFtp2")

loFtp.Hostname = "ftp.example.com"
loFtp.Username = "myFtpLogin"

//  Normally you would not hard-code the password in source.  You should instead obtain it
//  from an interactive prompt, environment variable, or a secrets vault.
loFtp.Password = "myPassword"

//  Connect and log in (Connect performs both).
llSuccess = loFtp.Connect()
if (llSuccess = .F.) then
    ? loFtp.LastErrorText
    release loFtp
    return
endif

//  NOOP does nothing on the server, but a successful reply confirms the control connection is
//  still responsive -- useful as a keep-alive during an otherwise idle session.
llSuccess = loFtp.Noop()
if (llSuccess = .F.) then
    ? loFtp.LastErrorText
    release loFtp
    return
endif

? "NOOP acknowledged by the server."

llSuccess = loFtp.Disconnect()
if (llSuccess = .F.) then
    ? loFtp.LastErrorText
    release loFtp
    return
endif



release loFtp