[ 
https://issues.apache.org/jira/browse/DISPATCH-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251517#comment-14251517
 ] 

Gordon Sim commented on DISPATCH-89:
------------------------------------

How would this interact with the 'fanout' option of the target address?

What about wildcard based matching on addresses themselves?  E.g. if the 
addresses are stocks.nyse.ibm, stocks.nasdaq.csco or whatever, could you match 
on stocks.nyse.*? I.e. I guess this is having the router detect on attach that 
some bindings should be created for the newly attached address (perhaps it 
needs to request some capability for this).

> 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
>
> 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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to