Github user bhardesty commented on a diff in the pull request:
https://github.com/apache/qpid-dispatch/pull/218#discussion_r151542358
--- Diff: doc/new-book/routing.adoc ---
@@ -213,15 +213,17 @@ address {
}
----
-`prefix` | `pattern`:: The address or group of addresses to which the
address settings should be applied. You can specify a prefix to match an exact
address or segment of an address. Alternatively, you can specify a pattern to
match an address using wildcards.
+`prefix` | `pattern`:: The address or group of addresses to which the
address settings should be applied. You can specify a prefix to match an exact
address or beginning segment of an address. Alternatively, you can specify a
pattern to match an address using wildcards.
+
//tag::prefix-matching[]
-A _prefix_ matches either an exact address or a segment within an address
that is delimited by either a `.` or `/` character. For example, the prefix
`my_address` would match the address `my_address` as well as `my_address.1` and
`my_address/1`. However, it would not match `my_address1`.
+A _prefix_ matches either an exact address or the beginning segment within
an address that is delimited by either a `.` or `/` character. For example, the
prefix `my_address` would match the address `my_address` as well as
`my_address.1` and `my_address/1`. However, it would not match `my_address1`.
//end::prefix-matching[]
+
//tag::pattern-matching[]
A _pattern_ matches an address that corresponds to a pattern. A pattern is
a sequence of words delimited by either a `.` or `/` character. You can use
wildcard characters to represent a word. The `*` character matches exactly one
word, and the `#` character matches any sequence of zero or more words.
+
+The pattern configuration and the address(es) that match the pattern
should use the same delimiter character. For example, if you configure the
pattern to be `my.+`, then the addresses that match the pattern should also use
a `.` as a delimiter (instead of a `/`).
--- End diff --
It sounds like I can just remove line 225 then. While it makes sense to
just use a single delimiter character (i.e. either "." or "/" but not both), it
sounds like Dispatch will still route messages correctly if the address and
configured pattern use a mixture of both types of delimiters.
Instead of line 225, I think we need a different statement about not using
reserved characters in message addresses. What do you think about this
(including the previous para for context):
> A pattern matches an address that corresponds to a pattern. A pattern is
a sequence of words delimited by either a `.` or `/` character. You can use
wildcard characters to represent a word. The `*` character matches exactly
one word, and the `#` character matches any sequence of zero or more words.
> The `*` and `/` characters are reserved as wildcards. Therefore, you
should not use them in the message address.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
