Custom FTP Server with virtual database backend

I need a FTP Server which is capable of the following: * For authentification it interacts with a table in a MySQL database (it's nice if other database engines were supported too, but not required) * Upon login, the user is supposed to see: a) A list of (virtual) files, which a read from another database table. These files only need to be listed - the user can't delete or download them (he can however replace them - see next point). b) various directories, which point to real directories in the file system. For example there might be a folder "images", which could be "/var/ftp/username/images/". I need to be able to change this directory configuration (add new ones, delete old ones). A configuration file is good, but if there is a *simple* way to do that in the code (constants, variables, whatever) and then recompile, that's ok too. * The user should be able to perform all standard FTP operations on the directories from b). He his interacting directly with the file system, as a normal FTP server does. The user needs to be able to upload a new file to his root directory. The uploaded file is then stored somewhere in the filesystem, and a row is written in the database table for that file. if the file already exists, it should be replaced. Other operations like download and delete don't have to be supported for those virtual files. * Continuation of aborted virtual downloads should be supported, if possible (please specify). * The server should be fast enough to handle at least up to 30 concurrent users, and, obviously, should be secure. The database layout needs to be configurable (again, code is ok). See attachment for example database layout. You can use whatever Free/OpenSource code is out there (please specify). A modified version of vsftpd, pureftpd, proftd etc. is good enough. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform The server needs to be able to run on a Debian Linux (Sarge) machine.