Minor Description
I have a use case where it would be useful for advisory messages to be (optionally) turned on for dispatched messages. There is currently an advisory for messages that have been consumed (acknowledged) but not for the dispatch before the acknowledge.
I will be adding a new hook to the broker API to do this so that it follows the same pattern as the other advisories such as delivered and consumed advisories. The existing methods for pre/post processing dispatch are called from the TransportConnection but the advisory logic should be called from the subscriptions themselves on dispatch so that things like the connection context can be easily passed and to better decide when to call it (such as not calling for the Queue NULL_MESSAGE type).
There will be a new policy entry flag called advisoryForDispatched that will be off by default.
