Rust

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 Rust Downloads

Download Chilkat for Rust

Rust


// 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.

let ftp = chilkat::Ftp2::new();

ftp.set_hostname("ftp.example.com");
ftp.set_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.
ftp.set_password("myPassword");

// Connect and log in (Connect performs both).
if ftp.connect().is_err() {
    println!("{}", ftp.last_error_text());
    return;
}

// 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.
if ftp.noop().is_err() {
    println!("{}", ftp.last_error_text());
    return;
}

println!("NOOP acknowledged by the server.");

if ftp.disconnect().is_err() {
    println!("{}", ftp.last_error_text());
    return;
}