[
https://issues.apache.org/jira/browse/DISPATCH-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042013#comment-17042013
]
Ken Giusti commented on DISPATCH-1578:
--------------------------------------
Also - and this is important - highlight the fact that a leading separator is
inferred. IOW specifying a leading separator is equivalent to not specifying
leading separator:
/foo/bar == foo/bar
.foo.bar == foo.bar == foo/bar
> Provide address pattern examples highlighting use of both pattern separator
> characters
> --------------------------------------------------------------------------------------
>
> Key: DISPATCH-1578
> URL: https://issues.apache.org/jira/browse/DISPATCH-1578
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 1.10.0
> Reporter: Ken Giusti
> Priority: Major
> Fix For: Backlog
>
>
> Folks have been tripped up on a subtle property of the address pattern
> matching syntax: that the separators '/' and '.' are equivalent. They've
> attempted to configure two patterns which actually overlap. Example:
>
> pattern: foo.bar
> and pattern: foo/bar
>
> The documentation does mention this, however it would probably be more
> obvious with an example. For example, highlight that
> foo.bar.baz == foo/bar/baz == foo.bar/baz == foo/bar.baz == etc
> The reason the router accepts both forms is that legacy applications tend to
> use the old amqp 0-10 pattern format ('.' is the separator) whilst the
> proposed AMQP addressing spec uses '/'.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
