Does the idea of an 'event driven producer' make sense?  One that receives
messages/exchange but doesn't necessarily produce one for every input?

My input comes in as bytes that need to be assembled.  A DefaultProducer
seems t have a process() which produces messages 1;1 which is not what I
need.  I need to programmatically determine whether or not to emit an
exchange, or do nothing (i.e. buffer it for a while until I have something
to output).

Reply via email to