| Home | All Classes | Main Classes | Annotated | Grouped Classes | Functions | |
The TQFtp class provides an implementation of the FTP protocol. More...
#include <ntqftp.h>
Inherits TQNetworkProtocol.
This class provides two different interfaces: one is the TQNetworkProtocol interface that allows you to use FTP through the TQUrlOperator abstraction. The other is a direct interface to FTP that gives you lower-level access to the FTP protocol for finer control. Using the direct interface you can also execute arbitrary FTP commands.
Don't mix the two interfaces, since the behavior is not well-defined.
If you want to use TQFtp with the TQNetworkProtocol interface, you do not use it directly, but rather through a TQUrlOperator, for example:
TQUrlOperator op( "ftp://ftp.trolltech.com" );
op.listChildren(); // Asks the server to provide a directory listing
This code will only work if the TQFtp class is registered; to register the class, you must call qInitNetworkProtocols() before using a TQUrlOperator with TQFtp.
The rest of this descrption describes the direct interface to FTP.
The class works asynchronously, so there are no blocking functions. If an operation cannot be executed immediately, the function will still return straight away and the operation will be scheduled for later execution. The results of scheduled operations are reported via signals. This approach depends on the event loop being in operation.
The operations that can be scheduled (they are called "commands" in the rest of the documentation) are the following: connectToHost(), login(), close(), list(), cd(), get(), put(), remove(), mkdir(), rmdir(), rename() and rawCommand().
All of these commands return a unique identifier that allows you to keep track of the command that is currently being executed. When the execution of a command starts, the commandStarted() signal with the command's identifier is emitted. When the command is finished, the commandFinished() signal is emitted with the command's identifier and a bool that indicates whether the command finished with an error.
In some cases, you might want to execute a sequence of commands, e.g. if you want to connect and login to a FTP server. This is simply achieved:
TQFtp *ftp = new TQFtp( this ); // this is an optional TQObject parent
ftp->connectToHost( "ftp.trolltech.com" );
ftp->login();
In this case two FTP commands have been scheduled. When the last scheduled command has finished, a done() signal is emitted with a bool argument that tells you whether the sequence finished with an error.
If an error occurs during the execution of one of the commands in a sequence of commands, all the pending commands (i.e. scheduled, but not yet executed commands) are cleared and no signals are emitted for them.
Some commands, e.g. list(), emit additional signals to report their results.
Example: If you want to download the INSTALL file from Trolltech's FTP server, you would write this:
ftp->connectToHost( "ftp.trolltech.com" ); // id == 1
ftp->login(); // id == 2
ftp->cd( "qt" ); // id == 3
ftp->get( "INSTALL" ); // id == 4
ftp->close(); // id == 5
For this example the following sequence of signals is emitted (with small variations, depending on network traffic, etc.):
start( 1 )
stateChanged( HostLookup )
stateChanged( Connecting )
stateChanged( Connected )
finished( 1, FALSE )
start( 2 )
stateChanged( LoggedIn )
finished( 2, FALSE )
start( 3 )
finished( 3, FALSE )
start( 4 )
dataTransferProgress( 0, 3798 )
dataTransferProgress( 2896, 3798 )
readyRead()
dataTransferProgress( 3798, 3798 )
readyRead()
finished( 4, FALSE )
start( 5 )
stateChanged( Closing )
stateChanged( Unconnected )
finished( 5, FALSE )
done( FALSE )
The dataTransferProgress() signal in the above example is useful if you want to show a progressbar to inform the user about the progress of the download. The readyRead() signal tells you that there is data ready to be read. The amount of data can be queried then with the bytesAvailable() function and it can be read with the readBlock() or readAll() function.
If the login fails for the above example, the signals would look like this:
start( 1 )
stateChanged( HostLookup )
stateChanged( Connecting )
stateChanged( Connected )
finished( 1, FALSE )
start( 2 )
finished( 2, TRUE )
done( TRUE )
You can then get details about the error with the error() and errorString() functions.
The functions currentId() and currentCommand() provide more information about the currently executing command.
The functions hasPendingCommands() and clearPendingCommands() allow you to query and clear the list of pending commands.
The safest and easiest way to use the FTP protocol is to use TQUrlOperator() or the FTP commands described above. If you are an experienced network programmer and want to have complete control you can use rawCommand() to execute arbitrary FTP commands.
See also TQt Network Documentation, TQNetworkProtocol, TQUrlOperator, TQHttp, and Input/Output and Networking.
This enum is used as the return value for the currentCommand() function. This allows you to perform specific actions for particular commands, e.g. in a FTP client, you might want to clear the directory view when a list() command is started; in this case you can simply check in the slot connected to the start() signal if the currentCommand() is List.
See also currentCommand().
This enum identifies the error that occurred.
See also error().
This enum defines the connection state:
See also stateChanged() and state().
If there is an unfinished command (i.e. a command for which the commandStarted() signal has been emitted, but for which the commandFinished() signal has not been emitted), this function sends an ABORT command to the server. When the server replies that the command is aborted, the commandFinished() signal with the error argument set to TRUE is emitted for the command. Due to timing issues, it is possible that the command had already finished before the abort request reached the server, in which case, the commandFinished() signal is emitted with the error argument set to FALSE.
For all other commands that are affected by the abort(), no signals are emitted.
If you don't start further FTP commands directly after the abort(), there won't be any scheduled commands and the done() signal is emitted.
Warning: Some FTP servers, for example the BSD FTP daemon (version 0.3), wrongly return a positive reply even when an abort has occurred. For these servers the commandFinished() signal has its error flag set to FALSE, even though the command did not complete successfully.
See also clearPendingCommands().
Example: network/ftpclient/ftpmainwindow.ui.h.
See also get(), readyRead(), readBlock(), and readAll().
The function does not block and returns immediately. The command is scheduled, and its execution is performed asynchronously. The function returns a unique identifier which is passed by commandStarted() and commandFinished().
When the command is started the commandStarted() signal is emitted. When it is finished the commandFinished() signal is emitted.
See also commandStarted() and commandFinished().
Example: network/ftpclient/ftpmainwindow.ui.h.
See also hasPendingCommands() and abort().
The stateChanged() signal is emitted when the state of the connecting process changes, e.g. to Closing, then Unconnected.
The function does not block and returns immediately. The command is scheduled, and its execution is performed asynchronously. The function returns a unique identifier which is passed by commandStarted() and commandFinished().
When the command is started the commandStarted() signal is emitted. When it is finished the commandFinished() signal is emitted.
See also stateChanged(), commandStarted(), and commandFinished().
Example: network/ftpclient/ftpmainwindow.ui.h.
This signal is emitted when processing the command identified by id has finished. error is TRUE if an error occurred during the processing; otherwise error is FALSE.
See also commandStarted(), done(), error(), and errorString().
Example: network/ftpclient/ftpmainwindow.ui.h.
This signal is emitted when processing the command identified by id starts.
See also commandFinished() and done().
Example: network/ftpclient/ftpmainwindow.ui.h.
The stateChanged() signal is emitted when the state of the connecting process changes, e.g. to HostLookup, then Connecting, then Connected.
The function does not block and returns immediately. The command is scheduled, and its execution is performed asynchronously. The function returns a unique identifier which is passed by commandStarted() and commandFinished().
When the command is started the commandStarted() signal is emitted. When it is finished the commandFinished() signal is emitted.
See also stateChanged(), commandStarted(), and commandFinished().
Example: network/ftpclient/ftpmainwindow.ui.h.
See also currentId().
Example: network/ftpclient/ftpmainwindow.ui.h.
This function can be used to delete the TQIODevice in the slot connected to the commandFinished() signal.
Example: network/ftpclient/ftpmainwindow.ui.h.
See also currentCommand().
This signal is emitted in response to a get() or put() request to indicate the current progress of the download or upload.
done is the amount of data that has already been transferred and total is the total amount of data to be read or written. It is possible that the TQFtp class is not able to determine the total amount of data that should be transferred, in which case total is 0. (If you connect this signal to a TQProgressBar, the progress bar shows a busy indicator if the total is 0).
Warning: done and total are not necessarily the size in bytes, since for large files these values might need to be "scaled" to avoid overflow.
See also get(), put(), and TQProgressBar::progress.
Example: network/ftpclient/ftpmainwindow.ui.h.
This signal is emitted when the last pending command has finished; (it is emitted after the last command's commandFinished() signal). error is TRUE if an error occurred during the processing; otherwise error is FALSE.
See also commandFinished(), error(), and errorString().
Example: network/ftpclient/ftpmainwindow.ui.h.
If you start a new command, the error status is reset to NoError.
The error string is often (but not always) the reply from the server, so it is not always possible to translate the string. If the message comes from TQt, the string has already passed through tr().
Example: network/ftpclient/ftpmainwindow.ui.h.
If dev is 0, then the readyRead() signal is emitted when there is data available to read. You can then read the data with the readBlock() or readAll() functions.
If dev is not 0, the data is written directly to the device dev. Make sure that the dev pointer is valid for the duration of the operation (it is safe to delete it when the commandFinished() signal is emitted). In this case the readyRead() signal is not emitted and you cannot read data with the readBlock() or readAll() functions.
If you don't read the data immediately it becomes available, i.e. when the readyRead() signal is emitted, it is still available until the next command is started.
For example, if you want to present the data to the user as soon as there is something available, connect to the readyRead() signal and read the data immediately. On the other hand, if you only want to work with the complete data, you can connect to the commandFinished() signal and read the data when the get() command is finished.
The function does not block and returns immediately. The command is scheduled, and its execution is performed asynchronously. The function returns a unique identifier which is passed by commandStarted() and commandFinished().
When the command is started the commandStarted() signal is emitted. When it is finished the commandFinished() signal is emitted.
See also readyRead(), dataTransferProgress(), commandStarted(), and commandFinished().
Example: network/ftpclient/ftpmainwindow.ui.h.
The command that is being executed is not considered as a scheduled command.
See also clearPendingCommands(), currentId(), and currentCommand().
The listInfo() signal is emitted for each directory entry found.
The function does not block and returns immediately. The command is scheduled, and its execution is performed asynchronously. The function returns a unique identifier which is passed by commandStarted() and commandFinished().
When the command is started the commandStarted() signal is emitted. When it is finished the commandFinished() signal is emitted.
See also listInfo(), commandStarted(), and commandFinished().
Example: network/ftpclient/ftpmainwindow.ui.h.
This signal is emitted for each directory entry the list() command finds. The details of the entry are stored in i.
See also list().
Example: network/ftpclient/ftpmainwindow.ui.h.
The stateChanged() signal is emitted when the state of the connecting process changes, e.g. to LoggedIn.
The function does not block and returns immediately. The command is scheduled, and its execution is performed asynchronously. The function returns a unique identifier which is passed by commandStarted() and commandFinished().
When the command is started the commandStarted() signal is emitted. When it is finished the commandFinished() signal is emitted.
See also commandStarted() and commandFinished().
Example: network/ftpclient/ftpmainwindow.ui.h.
The function does not block and returns immediately. The command is scheduled, and its execution is performed asynchronously. The function returns a unique identifier which is passed by commandStarted() and commandFinished().
When the command is started the commandStarted() signal is emitted. When it is finished the commandFinished() signal is emitted.
See also commandStarted() and commandFinished().
Make sure that the dev pointer is valid for the duration of the operation (it is safe to delete it when the commandFinished() is emitted).
Example: network/ftpclient/ftpmainwindow.ui.h.
Writes the data data to the file called file on the server. The progress of the upload is reported by the dataTransferProgress() signal.
The function does not block and returns immediately. The command is scheduled, and its execution is performed asynchronously. The function returns a unique identifier which is passed by commandStarted() and commandFinished().
When the command is started the commandStarted() signal is emitted. When it is finished the commandFinished() signal is emitted.
See also dataTransferProgress(), commandStarted(), and commandFinished().
The function does not block and returns immediately. The command is scheduled, and its execution is performed asynchronously. The function returns a unique identifier which is passed by commandStarted() and commandFinished().
When the command is started the commandStarted() signal is emitted. When it is finished the commandFinished() signal is emitted.
See also rawCommandReply(), commandStarted(), and commandFinished().
Example: network/ftpclient/ftpmainwindow.ui.h.
This signal is emitted in response to the rawCommand() function. replyCode is the 3 digit reply code and detail is the text that follows the reply code.
See also rawCommand().
Example: network/ftpclient/ftpmainwindow.ui.h.
See also get(), readyRead(), bytesAvailable(), and readBlock().
See also get(), readyRead(), bytesAvailable(), and readAll().
This signal is emitted in response to a get() command when there is new data to read.
If you specify a device as the second argument in the get() command, this signal is not emitted; instead the data is written directly to the device.
You can read the data with the readAll() or readBlock() functions.
This signal is useful if you want to process the data in chunks as soon as it becomes available. If you are only interested in the complete data, just connect to the commandFinished() signal and read the data then instead.
See also get(), readBlock(), readAll(), and bytesAvailable().
The function does not block and returns immediately. The command is scheduled, and its execution is performed asynchronously. The function returns a unique identifier which is passed by commandStarted() and commandFinished().
When the command is started the commandStarted() signal is emitted. When it is finished the commandFinished() signal is emitted.
See also commandStarted() and commandFinished().
Example: network/ftpclient/ftpmainwindow.ui.h.
The function does not block and returns immediately. The command is scheduled, and its execution is performed asynchronously. The function returns a unique identifier which is passed by commandStarted() and commandFinished().
When the command is started the commandStarted() signal is emitted. When it is finished the commandFinished() signal is emitted.
See also commandStarted() and commandFinished().
The function does not block and returns immediately. The command is scheduled, and its execution is performed asynchronously. The function returns a unique identifier which is passed by commandStarted() and commandFinished().
When the command is started the commandStarted() signal is emitted. When it is finished the commandFinished() signal is emitted.
See also commandStarted() and commandFinished().
See also State and stateChanged().
Example: network/ftpclient/ftpmainwindow.ui.h.
This signal is emitted when the state of the connection changes. The argument state is the new state of the connection; it is one of the State values.
It is usually emitted in response to a connectToHost() or close() command, but it can also be emitted "spontaneously", e.g. when the server closes the connection unexpectedly.
See also connectToHost(), close(), state(), and State.
Example: network/ftpclient/ftpmainwindow.ui.h.
This file is part of the TQt toolkit. Copyright © 1995-2007 Trolltech. All Rights Reserved.
| Copyright © 2007 Trolltech | Trademarks | TQt 3.3.8
|