camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAMEL-2934) Port the changed readLock to be avail for camel-ftp as well
Date Thu, 26 Aug 2010 08:29:40 GMT

     [ https://issues.apache.org/activemq/browse/CAMEL-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen updated CAMEL-2934:
-------------------------------

       Issue Type: New Feature  (was: Improvement)
    Fix Version/s: Future
                       (was: 2.5.0)
         Priority: Major  (was: Minor)

> Port the changed readLock to be avail for camel-ftp as well
> -----------------------------------------------------------
>
>                 Key: CAMEL-2934
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2934
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-ftp
>            Reporter: Claus Ibsen
>             Fix For: Future
>
>
> The {{changed}} read lock
> http://camel.apache.org/file2.html
> Is currently only avail for the file component. We should make it generic to leverage
the operations API so we can use it from FTP also.
> And we should allow URI parameters to configure it using {{readLock.}} prefix, so you
can do
> {{readLock.timeout=5000&readLock.changedInterval=2000}}
> This means the {{readLockTimeout}} should be @deprecated as we just leverage the Camel
prefix properties mechanism to auto set the options.
> The {{changed}} read lock should also have a new option to set the _steady_ interval.
The time period in which the file must *not* have been changed. Currently its fixed to 1 second.
But end users could set it to 5 sec. to ensure that the file hasn't been touched for that
min. period.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message