You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2016/09/06 14:47:22 UTC
[jira] [Updated] (QPID-6391) [C++ Broker] [AMQP 1.0] add support
for a 'no-local' filter
[ https://issues.apache.org/jira/browse/QPID-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Ross updated QPID-6391:
------------------------------
Fix Version/s: qpid-cpp-1.35.0
> [C++ Broker] [AMQP 1.0] add support for a 'no-local' filter
> -----------------------------------------------------------
>
> Key: QPID-6391
> URL: https://issues.apache.org/jira/browse/QPID-6391
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker
> Affects Versions: 0.31
> Reporter: Robbie Gemmell
> Assignee: Gordon Sim
> Priority: Minor
> Fix For: qpid-cpp-1.35.0
>
>
> The JMS clients support the idea of 'no-local' on topic subscriptions/consumers. This means that that subscribers/consumers dont receive messages published by the same connection or, in the case of durable subscriptions, by any connections with the same ClientID.
> Both the JMS clients currently use the following filter (from \[1\]) to denote this:
> {noformat}
> <type name="no-local-filter" class="composite" source="list" provides="filter">
> <descriptor name="apache.org:no-local-filter:list" code="0x0000468C:0x00000003"/>
> </type>
> {noformat}
> It is likely that the AMQP JMS Mapping will eventually define its own filter for this, but the expected behaviour should be the same.
> \[1\] https://svn.apache.org/repos/asf/qpid/trunk/qpid/specs/apache-filters.xml#type-no-local-filter
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org