Niklas Gustavsson wrote:
Niklas Therning wrote:
It makes sense I think! Would we still keep codec implementations in
subprojects under mina/ (like filter-codec-http)? I think that's a
nice separation. It would be great if the codec parts of ftpserver
could be separated from its use in ftpserver and become
filter-codec-ftp. Is that doable?
Yes, that would most certainly be doable. However, not incredibly
useful I'm afraid. FTP commands are very simplistic when compared to,
for example, HTTP. For example, there is nothing like HTTP headers in
FTP commands, only the command and an argument. For example:
STOR myfile.txt
That being said, if you still would like a separate FTP codec I'll
have a go at doing the coding :-)
/niklas
Well, I see your point and I totally agree that it wouldn't be very
useful to do this with the FTP stuff. My main concern was to simplify
for users to integrate HTTP/FTP/whatever functionality into their apps.
But it seems like just having the codec won't be very useful. I guess it
would make more sense to make sure ftpserver, AsyncWeb, etc are easily
embeddable. AsyncWeb in particular (e.g. admin interface, web service
interface). Maybe they already are?
/Niklas (T)
