I'm resending this message as there hopefully some more people on the list now.

Hi

Hopefully most of the people with interest in FTPServer has now started subscribing to the mailing list :-)

As described by Paul, the FTPServer design somewhat clashes with the aim for IoC friendly, reusable code as it binds our implementations into a FTPServer specific interfaces (e.g. Component). I think a few first steps to correct this would be: 1. Remove Component interface, make implementations (e.g. UserManager) into POJOs
2. Remove config classes , use setters instead
3. Make FtpServer initialize a default server implementation, customizable by users if necessary (according to the comments by Paul, Niclas and Craig) much like Jetty.
4. Define an easy API for initalizing a Ftplet from code (like Jetty)
5. Define a XML schema for adding Ftplets (again like Jetty but possibly with XML more like web.xml)

What do you think? If you are happy with this approach I will start hacking away and submitting patches.

/niklas

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to