fakeftpserver-features.apt revision 5f5f353cd125c9170fb14edc89e4043c8ceacc60 
1		--------------------------------------------------
2				FakeFtpServer Features and Limitations
3		--------------------------------------------------
4
5FakeFtpServer Features
6
7  * Standalone dummy FTP server. Run either within the same JVM as test code or in a different JVM.
8
9  * Implements common FTP server commands.
10
11  * Works out of the box with reasonable and expected behavior. Can simulate most mainline success and error scenarios.
12
13  * In most cases, requires little or no knowledge or understanding of FTP server commands and reply codes. 
14
15  * Provides a simulated server file system, including support for file and directory permissions and owner and
16   group authorization based on Unix. This file system can be populated at startup (or thereafter) with
17   directories and files (including arbitrary content) to be retrieved by an FTP client. Any files sent to the server
18   by an FTP client exist within that file system as well, and can be accessed through the file system API, or
19   can even be subsequently retrieved by an FTP client.
20
21  * Supports active and passive mode data transfers.
22
23  * Fully supports configuration within the <<Spring Framework>>.
24  
25  * Can be used to test FTP client code written in any language
26  
27
28FakeFtpServer Limitations
29
30  Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Features and
31  scenarios not supported include:
32
33  * Leaving the data connection open across multiple client requests.
34
35  * Transmission mode other than 'Stream'. The STRU command is implemented but has no effect (NOOP).
36
37  * Data Types other than ASCII and IMAGE (binary).
38
39  * Vertical Format Control other than the default (NON PRINT).
40
41  * Record Structure and Page Structure. The STRU command is implemented but has no effect (NOOP).
42
43  * Error Recovery and Restart. The REST command is implemented but has no effect (NOOP).
44
45  * Structure Mount. The SMNT command is implemented but has no effect (NOOP).
46
47  * Abort. The ABOR command is implemented but has no effect (NOOP).
48
49  * Allocate. The ALLO command is implemented but has no effect (NOOP).
50
51  []
52
53  For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instead, which
54  provides a lower-level abstraction and finer control over exact server reply codes and responses.
55
56  
57