It seems from the documentation that the multicast function would actively
copy the http message to both destinations. That should be disregarding a
caching, or non caching http client.
/**
* Multicasts messages to all its child outputs; so that each processor
and
* destination gets a copy of the original message to avoid the
processors
* interfering with each other.
*/
public MulticastType multicast() {
I should of course be reading code instead of documentation :-) but that is
a bit too much after only 1 day of Camel riding.
--
View this message in context:
http://www.nabble.com/usage-of-multicast-tp23163812p23169979.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.