I'm developing my first component, so please go easy on me with my stupid questions.
First of all I'm not sure whether a endpoint 'processor' that receives a request, access an external system and return results is properly called a 'consumer' or a 'producer'. On one hand it 'produce' requests to the external system, on the other hand it thereafter 'consumes' requests from the external system. I call it a 'producer' in the following. I have a producer that request data from an underlying database (Solr) and receives possibly hundred of thousands of results. And some callers wants all. I therefore do not want to create a gigantic OUT body with all results. Instead I would like to 'stream' the results to the caller as I get them in batches of a few hundred. Is the proper way of doing this to create a 'request' route and a 'respond' route, then let the caller issue the request on the 'request' route and thereafter read from the 'respond' route until done? How does the caller know that the last message has been received? -- View this message in context: http://camel.465427.n5.nabble.com/Streaming-data-back-from-Producer-tp4584173p4584173.html Sent from the Camel Development mailing list archive at Nabble.com.
