Up to 20 simultaneous connections, a hundred or so connections a day
and several hundred megabytes of data a day - mostly pdf and xml files.
This isn't that extreme, just want to make sure I don't make a choice I
regret, if I hook up apache ftp. The reason why I want to use java, over
proftpd, is the service is "put" only, once the files are delivered
they are moved elsewhere for processing - at the moment it scans the
disk for file additions, figured a messaging based solution would be
more robust.
Mark
Niklas Gustavsson wrote:
Mark Proctor wrote:
sorry not SFTP, I meant just ssl - SFTP is a SSH server subsystem, I
guess thats out of scope for the apache FTP project.
Also what's the stability and scalability like, compared to say proftpd?
Mark
Mark Proctor wrote:
Whats the status on out of the box SFTP - is it 100%? assuming
clients can only upload, is it acceptable for that?
It should be 100% for all operations (e.g. upload, download, list).
Please tell me if that's not true because that's a bug then :-)
We should also support both explicit and implicit SSL (as instructed
by the client with AUTH or by having an SSL socket to start with) as
well as security of the data channel (via PROT).
When it comes to performance and scalability I'm not sure. Since
protftp has been around for so long and got so much usage, while we
haven't (as far as I know) spent so much time on performance, my bet
would be on protftp for now.
As just discussed on this list, I'm looking into moving us onto MINA.
MINA seems to have great performance numbers so I'm hoping that should
help us a long way.
Do you have any specific numbers in mind as for performance and
scalability? Might be worth testing with our perf-test module.
/niklas
