camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laurentiu Trica (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-2934) Port the changed readLock to be avail for camel-ftp as well
Date Fri, 01 Jul 2011 09:42:28 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058273#comment-13058273
] 

Laurentiu Trica commented on CAMEL-2934:
----------------------------------------

I'm glad I could help.
I think we could improve the gathering of file modification / size details but we need to
add specific operations to the FtpOperations and Sftpperations classes - and surely to the
GenericFileOperations - that get this info by sending a specific command to the servers.

> Port the changed readLock to be avail for camel-ftp as well
> -----------------------------------------------------------
>
>                 Key: CAMEL-2934
>                 URL: https://issues.apache.org/jira/browse/CAMEL-2934
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-ftp
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.8.0
>
>         Attachments: FtpChangedLockStrategy.java, FtpProcessStrategyFactory.java, SftpChangedLockStrategy.java,
SftpProcessStrategyFactory.java, ftp, ftps, sftp
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message