This project has moved and is read-only. For the latest updates, please go here.

Client FTP Drive Letter Mapper

May 25, 2011 at 6:14 PM

This is to become the discussion list for the solution to getting "Amazing" throughput in both directions to a FTP server (Read Liquesce FTP Pool :-)

So please add your wish list / requirements here.

May 25, 2011 at 6:14 PM

Top Level Requirements:
- .Net 4 Client profile
- Has to be x32 due to Dokan restrictions
- Per user configurations
- More than one drive letter per user
- Has to show drive as a netwrok drive (This will ease some of the security issues Win2k8 issues)
- Application tray
- Logging
- Management
- - - Username Encryption in config
- - - Password Encryption in config
- - - Preferred drive letter
- - - Access rights expected (Need to have some way of testing)

Wish List:
- Some way of telling how much space is actually on the target drive letter
- Use of advanced FTP features for REST

May 25, 2011 at 6:16 PM

Will investigate the usage of this library "" instead.

May 25, 2011 at 6:16 PM

Turns out that the StarlSoftFtps code base was a good place to start, BUT, it has a few issues that I have had to Iron out:

May 25, 2011 at 6:16 PM
Edited May 25, 2011 at 6:17 PM

Use of UTF8 is not consistent with FTP RFC
StarlSoftFtps code base always sends all commands etc in UTF8 this is incorrect.
Also, as it does not issue the OPTS utf8 on command, then all answers will default to ASCII, but the code base assumes UTF8 !