I did notice the localWorkDirectory option and gave that some thought. But since I am dealing with medical data there HIPPA concerns and then I would have to factor in security concerns related to storing these files on a local directory. I think at this point I am will to pay the performance penalty of each entire message being contained within a message.
So ultimately it seems like my best option is the two routes. One to pull via ftp, the other as SEDA for subsequent concurrent processing. But I noticed that setting concurrentConsumers=# will always force # number of threads to be created. I need more of a thread pooling scheme and maybe that's available. I just have not yet had the time to explore the documentation or the book regarding that. -- View this message in context: http://camel.465427.n5.nabble.com/is-FTP2-asynchrounus-tp3261083p3262236.html Sent from the Camel - Users mailing list archive at Nabble.com.
