[
https://issues.apache.org/jira/browse/DISPATCH-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336200#comment-16336200
]
ASF GitHub Bot commented on DISPATCH-89:
----------------------------------------
Github user kgiusti commented on a diff in the pull request:
https://github.com/apache/qpid-dispatch/pull/244#discussion_r163335294
--- Diff: python/qpid_dispatch/management/qdrouter.json ---
@@ -1126,6 +1126,106 @@
}
},
+ "router.config.exchange": {
+ "description":"[EXPERIMENTAL] Defines a topic exchange.",
+ "extends": "configurationEntity",
+ "operations": ["CREATE", "DELETE"],
+ "attributes": {
+ "address": {
--- End diff --
We haven't been very good at being consistent with naming: the router.node
itself has an "address" attribute, while the config.autoLink's address is
labeled with 'addr'.
There are a few attributes that have 'addr' as a prefix or a suffix to the
full name, e.g.:
addrCount, owningAddr, and externalAddr.
So we're already inconsistent to some degree. I'd favor using 'address' as
the attribute name for an entity that has a single address attribute, and use
the "<prefix>Addr" for those entities with more than one address attribute. So
my opinion is to keep the 'address' as is.
However, I'm no UI expert by any means. Hmmm.... Let me see if I can
channel the Ghost of Steve Jobs and see what his reaction is....
<Ghost of Steve Jobs>
Don't be consistent - be Brave!!!
Oh, and you're holding that wrong....
</Ghost of Steve Jobs>
jk! ;D
> Model the legacy topic exchange behavior of qpidd
> -------------------------------------------------
>
> Key: DISPATCH-89
> URL: https://issues.apache.org/jira/browse/DISPATCH-89
> Project: Qpid Dispatch
> Issue Type: New Feature
> Components: Routing Engine
> Affects Versions: 0.2
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Priority: Major
>
> With Qpidd, a user can define a binding from an Exchange to a target queue.
> The binding uses a key that is compared to a message's subject field. If the
> key matches, the message is routed to the target queue for that binding.
> It should be possible to emulate this behavior using the dispatch router.
> Example:
> User defines a mappings from a target address (the 'exchange') to a different
> target address(es) (the 'queue'). These mappings (the 'bindings') are driven
> by a pattern match against the inbound message's subject field.
> Messages arriving at the router from any link whose target address has
> bindings defined are not immediately routed. Prior to routing, the message's
> subject field is extracted and compared against each binding defined for the
> target. A list of new target addresses is created containing the target
> address from each binding that satisfied the pattern match. The message is
> then routed to each new target address.
> The pattern syntax should be the same 'dotted string' notation from qpidd,
> including '*' and "#' wildcarding.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
