android_mt6572_jiabo/external/mockftpserver/MockFtpServer
2025-09-05 16:56:03 +08:00
..
.settings first commit 2025-09-05 16:56:03 +08:00
src first commit 2025-09-05 16:56:03 +08:00
.classpath first commit 2025-09-05 16:56:03 +08:00
.project first commit 2025-09-05 16:56:03 +08:00
CHANGELOG.txt first commit 2025-09-05 16:56:03 +08:00
LICENSE.txt first commit 2025-09-05 16:56:03 +08:00
MockFtpServer.eml first commit 2025-09-05 16:56:03 +08:00
MockFtpServer.iml first commit 2025-09-05 16:56:03 +08:00
MockFtpServer.ipr first commit 2025-09-05 16:56:03 +08:00
pom.xml first commit 2025-09-05 16:56:03 +08:00
README.txt first commit 2025-09-05 16:56:03 +08:00

MockFtpServer version ${project.version}
-------------------------------------------------------------------------------
${project.url}

The MockFtpServer project provides mock/dummy FTP server implementations for testing FTP client
code. Two FTP Server implementations are provided, each at a different level of abstraction.

FakeFtpServer provides a higher-level abstraction. You define a virtual file system, including
directories and files, as well as a set of valid user accounts and credentials. The FakeFtpServer
then responds with appropriate replies and reply codes based on that configuration.

StubFtpServer, on the other hand, is a lower-level "stub" implementation. You configure the
individual FTP server commands to return custom data or reply codes, allowing simulation of
either success or failure scenarios. You can also verify expected command invocations.

MockFtpServer is written in Java, and is ideally suited to testing Java code. But because
communication with the FTP server is across sockets and TCP/IP, it can be used to test FTP client 
code written in any language.

See the online documentation for more information.

See the FTP Protocol Spec (http://www.ietf.org/rfc/rfc0959.txt) for information about 
FTP, commands, reply codes, etc..

DEPENDENCIES

MockFtpServer requires 
 - Java (JDK) version 1.4 or later
 - The Log4J jar, version 1.2.13 or later, accessible on the CLASSPATH
   (http://logging.apache.org/log4j/index.html).