[
https://issues.apache.org/jira/browse/AMQ-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799096#comment-13799096
]
Dmitry Salychev edited comment on AMQ-4815 at 10/18/13 1:28 PM:
----------------------------------------------------------------
Please, put me in the right way of code digging routine for creating the patch.
was (Author: dsalychev):
Please, put me in the right way of code digging routine.
> Providing additional advisory options on per-destination basis
> --------------------------------------------------------------
>
> Key: AMQ-4815
> URL: https://issues.apache.org/jira/browse/AMQ-4815
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: Dmitry Salychev
> Priority: Minor
>
> I want to deal with advisory messages only for specified destinations and
> avoid all advisory messages from other to achieve as small as possible memory
> and connections overhead.
> This is can be done on a per-destination basis like that:
> {noformat}
> <broker advisorySupport="true" ...>
> ...
> <destinationPolicy>
> <policyMap>
> <policyEntries>
> <policyEntry topic="api.>" creatingAdvisory="true"/>
> ...
> {noformat}
> In the background, I want to use
> org.apache.activemq.advisory.DestinationSource(It is based on the advisory
> messages from ActiveMQ.Advisory.Topic, isn't it?) for many topics on many
> brokers with minimum overhead.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
