Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <12396658.post@talk.nabble.com>
Date: Wed, 29 Aug 2007 15:00:53 -0700 (PDT)
From: Nicky Sandhu <karajdaar@gmail.com>
To: camel-dev@activemq.apache.org
Subject: Producer Consumer concepts need to be clarified
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I am still not clear on the contractual difference between a Producer and
Consumer. My context is the wiring service provided in OSGi and there is a
clearly defined Producer and Consumer relationship, ie a Producer is
something that can be polled and a Consumer is something that can be updated
with a polled value. Ofcourse something can be both a Producer and Consumer

In Camel's case Producer and Consumer are both Services (that is share
lifecycle concepts such as start and stop). A Producer is a just a processor
that can create exchanges in addition to being able to modify the in and out
messages of the exchanges, no production semantics in the interface? A
consumer is just a service, no consumption contract in interface ??

Can someone explain the intent of the Producer/Consumer concepts ? Is the
vagueness deliberate...it gives  more freedom to experiment ...?


-- 
View this message in context: http://www.nabble.com/Producer-Consumer-concepts-need-to-be-clarified-tf4350719s22882.html#a12396658
Sent from the Camel - Development mailing list archive at Nabble.com.