That's pretty much what we were describing. I see there is no DSL for this so beyond it being a known algorithm it remains a "write-your-own-implementation". I guess therefore it's a relatively narrow use-case...
On 4 November 2016 at 16:50, Quinn Stevenson <qu...@pronoia-solutions.com> wrote: > I think the EIP you’re referring to is the “Claim Check” pattern ( > http://www.enterpriseintegrationpatterns.com/patterns/messaging/ > StoreInLibrary.html <http://www.enterpriseintegrationpatterns. > com/patterns/messaging/StoreInLibrary.html> ), and Camel does support > that EIP ( http://camel.apache.org/claim-check.html < > http://camel.apache.org/claim-check.html> ) > > HTH > > > > On Nov 4, 2016, at 8:53 AM, James Green <james.mk.gr...@gmail.com> > wrote: > > > > Hi, > > > > We are preparing to start handling very large messages. Currently we have > > small (<1k) messages arriving from message queues and being processed, > but > > these new messages could be several mb each. > > > > Each message is basically a JSON formatted payload with metadata and a > > content-body. It's this content-body that may end up being much larger in > > some cases. > > > > We have speculated that this may be best handled by recognising a > reference > > within the message meta-data to a URI that actually has the content-body. > > This feels like a pattern that may have already been invented. Not unlike > > SOAP where references to files sent separately can be achieved. > > > > Anyone know of such a system or even terms to hit Google with? And might > > there be something in the Camel-sphere that loads external references > > already? > > > > Thanks, > > > > James > >
