Part LI. FTP Client for eCos TCP/IP Stack
The ftpclient package provides an FTP (File Transfer Protocol) client for use with the TCP/IP stack in eCos. It supports both IPv4 and IPv6 and will use the DNS client, when its is part of the eCos configuration. The API allows for active (server->client) or passive (client->server) transfer connections to be used.
The data operations support binary mode transfers only. The supplied filename paths only support Unix-style ’/‚ directory separators.
The API provides support for either direct buffer transfers, or for call-back routines to be used to copy data as required. Care must be taken, especially when receiving files, since the direct buffer support calls are limited to handling files that will fit within the single buffer passed through the API. The API call-back based implementation can avoid this limitation by allowing the client to control the data reception and buffering as appropriate.
By default the data transfer operations will initially attempt a
connection using the newer “extended” (IPv6 capable) FTP
commands (EPRT
or EPSV
as
appropriate). If those commands are not supported by the FTP server
then the client will fallback to using the original FTP connection
commands (PORT
or PASV
respectively).
Table of Contents
- 188. FTP Client API and Configuration
- 188.1. FTP Client API
- 188.1.1. Support API
- 188.1.2. ftp_delete
- 188.1.3. ftpclient_printf
- 188.1.4. Basic FTP Client API
- 188.1.5. ftp_get
- 188.1.6. ftp_put
- 188.1.7. ftp_get_var
- 188.1.8. ftp_put_var
- 188.1.9. Extended FTP Client API
- 188.1.10. ftp_get_extended
- 188.1.11. ftp_put_extended
- 188.1.12. ftp_get_extended_var
- 188.1.13. ftp_put_extended_var
- 188.2. FTP Client Configuration
2024-12-10 | Open Publication License |