Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Message-ID: <2043005304.1222189072662.JavaMail.jira@brutus>
Date: Tue, 23 Sep 2008 09:57:52 -0700 (PDT)
From: "Jayson Minard (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Created: (CAMEL-933) Implement the Claim-Check EIP pattern
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Implement the Claim-Check EIP pattern
-------------------------------------

                 Key: CAMEL-933
                 URL: https://issues.apache.org/activemq/browse/CAMEL-933
             Project: Apache Camel
          Issue Type: New Feature
          Components: eip
    Affects Versions: 1.4.0
            Reporter: Jayson Minard


Add the Claim-Check EIP pattern to Camel allowing a process to store an out of band object and receive a claim ticket that can then be used by a later process to retrieve the object.  

An example of this pattern is implemented in ActiveMQ via [BlobMessages|http://activemq.apache.org/blob-messages.html] which allows out-of-band storage of a stream of data by HTTP, FTP, SCP or other protocols.

A benefit to the system is that you can allow data that cannot reasonably go into a message to be carried along with the message (by the claim ticket) and only retrieved when needed or appropriate.  Examples of that include overly large files that should not be routed to nodes that do not use the body of the file; or secure information that needs to be made available to nodes but not contained within the messaging system.

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