This might be a slightly weird question, but what does making an exchange persistent actually do?
What I mean is that one of the behaviours that I'd really like with Qpid is to be able to have *configuration* persisted.
With queues if I make the queue durable then I end up with queue config that survives broker restarts, but unfortunately (for my scenario) I also end up with a queue that persists messages and gives me a performance hit etc. which I don't want.
So what about exchanges? If I create an exchange marked as durable does this simply persist the exchange configuration and allow it to be recreated automatically on broker restart or does it also mess with messages (in other words does a durable exchange do anything specific on the message flow performance critical path that might affect message flow performance?)
Does anyone have any thoughts on how easy it might be to add a switch like "durable-config" (as opposed to "durable") to queue creation. I've got a nasty feeling that it might be harder than it sounds as I think that queues can be created via QMF and also by underlying queueDeclare methods (I *think* qpid-config and Address parsing use the latter) so I guess that one would have to be careful to avoid breaking anything that relies on the current method signature.
MTIA Frase --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
