PowerBuilder
PowerBuilder
Disconnect from an FTP Server
See more FTP Examples
Demonstrates the Chilkat Ftp2.Disconnect method, which ends the FTP session and closes the control connection. It takes no arguments. When connected, Chilkat sends QUIT and then closes the socket.
Background: Sending
QUIT before closing is the polite shutdown — it lets the server finalize the session cleanly rather than seeing an abrupt socket drop. The method is idempotent, so calling it when nothing is connected, or a second time after the session is already closed, still succeeds; that makes it safe to put in cleanup paths without guarding it.Chilkat PowerBuilder Downloads
integer li_rc
integer li_Success
oleobject loo_Ftp
li_Success = 0
// Demonstrates the Ftp2.Disconnect method, which ends the FTP session and closes the control
// connection. It takes no arguments. When connected, Chilkat sends QUIT and then closes the
// socket.
loo_Ftp = create oleobject
li_rc = loo_Ftp.ConnectToNewObject("Chilkat.Ftp2")
if li_rc < 0 then
destroy loo_Ftp
MessageBox("Error","Connecting to COM object failed")
return
end if
loo_Ftp.Hostname = "ftp.example.com"
loo_Ftp.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.
loo_Ftp.Password = "myPassword"
// Connect and log in (Connect performs both).
li_Success = loo_Ftp.Connect()
if li_Success = 0 then
Write-Debug loo_Ftp.LastErrorText
destroy loo_Ftp
return
end if
// ... perform FTP operations ...
// Disconnect is idempotent: calling it when no connection exists, or calling it again after the
// session is already closed, still succeeds.
li_Success = loo_Ftp.Disconnect()
if li_Success = 0 then
Write-Debug loo_Ftp.LastErrorText
destroy loo_Ftp
return
end if
Write-Debug "Disconnected."
destroy loo_Ftp