Since I did make my tool work with v2, and I am currently discarding v1 messages (*), I think that this won't impact me.
(* I have to discard the v1 messages, since we are not, as previously proposed, delivering the v2 messages to a separate Console (callback) method. So I'm slightly less certain that this isn't a problem than I would have been if I could have simply not over loaded the v1 methods. But I've been in there with pdb, and I'm pretty sure.) I do wonder if there are other folks using this interface who also read this list, since I seem to be the only squeaky wheel. Bill On Fri, Jul 12, 2013 at 3:17 PM, Ken Giusti <[email protected]> wrote: > Folks, > > I've made a change on trunk to the way the C++ Broker generates > unsolicited management update messages (i.e. object update notification > messages and event messages). [1] > > Previous to this change, the broker would transmit two messages for each > management event and object update - one in the old QMFv1 binary format, > and one in the QMFv2 AMQP Map format. This change disables the send of the > QMFv1 binary version of the message. The new broker default behavior is to > send only one message per event/update, in the QMFv2 map format. >
