2009/1/27 Andi Abes <aa...@progress.com>: > Having finally caught up with the discussion about header/property > copying and propagation, I thought it might be interesting to circle > back to the original question Claus posed (slightly reworded) - what is > the purpose of the out message? > > As a "flame generator" question - > If the exchange only carried 1 message, where each component in turn got > to use and optionally modify. > - how would this be different than the current pipeline behavior ? > Currently if a component sets an out message, it is effectively > replacing the in message for the next one. > > - would it not simplify the whole issue of header copying/propagation? > No copying is necessary since it is the same message that travels > through the route > > As an optional augmentation of this model, an exchange could carry 2 > messages > - the "current" or "working" message, which will eventually be the > output of the exchange > - a readonly primordial input message, as provided by the user. > > > (start the flame...)
Flame was already started some time ago here: http://www.nabble.com/in-out-fault-messages-discussion-to14170013s22882.html#a14170013 You can go through it if you want ;) Roman
