camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: What are the differences between using preMove and readLock=rename
Date Tue, 30 Aug 2011 09:04:57 GMT
Hi

readLock is a locking feature. This comes before any processing of the
file. At first Camel needs to obtain a lock on the file.
For that you can use different locking strategies. One of these is
readLock=rename. This will do a IO rename of the file, and then rename
the file back again. This is based on the assumption a lock can be
obtained on the file, if you could do a IO rename on the file.


preMove is part of the process where Camel got the read lock on the
file, and is about to process the file.
The preMove option will just move the file *before* the file is
processed. For example some use cases requires you to move in progress
files to a specific folder etc. This is what you can use this option
for.



On Mon, Aug 29, 2011 at 8:48 PM, bbuzzard
<Billy.Buzzard@bnsflogistics.com> wrote:
> Both of these functions seem like they are doing basically the same thing.
> What are the advantages and disadvantages of using one method verses the
> other?
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/What-are-the-differences-between-using-preMove-and-readLock-rename-tp4747269p4747269.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Mime
View raw message