Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Message-ID: <2012331635.1228204565392.JavaMail.jira@brutus>
Date: Mon, 1 Dec 2008 23:56:05 -0800 (PST)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-1099) File consumer should keep track of
 processed files
In-Reply-To: <1529157155.1227064565385.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen commented on CAMEL-1099:
------------------------------------

Jon, others?

Any good ideas of the file based repository?

I am wondering if we should
- have the LRUCache as a 1st level cache, and have write through to the file store when adding, using append
- load the filestore on startup
- configurable filename and folder
- use camel file component to read/write (configuration could then be a file endpoint = "file://data/idempotentrepository.txt?append=true&autoCreate=true")

> File consumer should keep track of processed files
> --------------------------------------------------
>
>                 Key: CAMEL-1099
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1099
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core, camel-ftp, camel-spring
>            Reporter: Jonathan Anstey
>            Assignee: Claus Ibsen
>             Fix For: 2.0.0
>
>
> See thread: http://www.nabble.com/Deprecation-of-file-consumer-timestamp-td20566034s22882.html
> Will be following Gert's suggestion of multiple implementations for the storage mechanism so many use cases can be covered:
> - an in-memory store for testing purposes
> - a file-based implementation for basic production environments
> - a database- or ldap-backed implementation for clustered environments, where a file can arrive through multiple directories

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