Hi You can have it use a localWorkDirectory which means it will stream directly to file. But then you should not have to do any deletion/move the file afterwards.
However if you need to move / delete the downloaded file then you should store it to a file And then have a 2nd route which pickup those files which they can process async. So the 1st route is sync. The 2nd route is async / concurrent, but it consumes the local files instead of the FTP. Then you can use the seda / threads to turn the route into async from that point forward. On Thu, Nov 11, 2010 at 10:28 PM, awold <[email protected]> wrote: > > Opps, I think the answer was staring me right in the face in the > documentation. > > > > FTP Consumer does not support concurrency > The FTP consumer (with the same endpoint) does not support concurrency (the > backing FTP client is not thread safe). > You can use multiple FTP consumers to poll from different endpoints. It is > only a single endpoint that does not support concurrent consumers. > The FTP producer does not have this issue, it supports concurrency. > > In the future we will add consumer pooling to Camel to allow this consumer > to support concurrency as well. > > -- > View this message in context: > http://camel.465427.n5.nabble.com/is-FTP2-asynchrounus-tp3261083p3261140.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
