Don't think I need JMS, at this stage, I was just going to use jakarta
pipeline to get the files processed. But JMS for the future would be
useful.
Mark
Niklas Gustavsson wrote:
Mark Proctor wrote:
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.
I think that the number of concurrent connections will be your first
limiting factor. However, I have used the perf-test module to test 100
concurrent connections (three different test scenarios: noop, retrive
and store) on my laptop without any issues.
But, I would note that FtpServer has not yet been heavily tested nor
optimized for performance or scalability. But of course we're happy to
work with you if you run into any troubles!
If you with "messaging based solution" mean JMS support you might be
in luck. I got a JMS backed file system implementation on my todo
list. If you would like to work with me on this I would be happy to :-)
/niklas
