Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <386184086.1234461659359.JavaMail.jira@brutus>
Date: Thu, 12 Feb 2009 10:00:59 -0800 (PST)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-1295) FTPConsumer to support storing
 remote payload in local file directory
In-Reply-To: <2014088607.1232878259364.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-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49407#action_49407 ] 

Claus Ibsen commented on CAMEL-1295:
------------------------------------

Got the basic done now.

So you can do:
{code}
from("ftp:somewhere?localDirectory=/tmp").to"("file://inbox");
{code}

And Camel will pass a java.io.File as the body, so when the file producer is writing the file in the inbox directory it will use the file handle given from the ftp consumer.

This allows us to:
- avoid reading the ftp content into memory
- storing directly to local files
- and pass file handles to file producer so it can do fast file channel stuff for writing files.

> FTPConsumer to support storing remote payload in local file directory
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-1295
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1295
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-ftp
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: Future
>
>
> Use of local work directory to store remote content directly in a file. So you avoid reading 2gb in memory if you consume very big files.

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