>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)
As i spoked with Rana, we (my self, and some friends) are
developing a similar solution called JFTP4I (Java FTP for Integration),
that's basically an application server for the FTP protocol. The solution
will manage different applications deployed in the server (*.far -> Ftp
Archive Resources) for different resources and requests. The current
implementation already has a descriptor (XML), so i think we can really
help on that issue (4 and 5). Rana has asked me for the source code, and i
gladly sended to him.
I don´t know how we can participate on the JFTPServer developing
process (or better, how we can?), but we really would like to.
Maybe you could help us on that.
[]s,
João
>> What do you think? If you are happy with this approach I will start
>> hacking away and submitting patches.
>>
>> /niklas
