[
https://issues.apache.org/jira/browse/DISPATCH-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249976#comment-15249976
]
Alan Conway commented on DISPATCH-286:
--------------------------------------
At this point you are really talking about pattern matching. Beware of
starting a simplistic solution that becomes unmanageably complex as new
requirements are added willy-nilly. I suggest an extensible set of pattern
types, you already have 3 - slash-separated, dot-separated,
backslash-separated. That way you can keep the efficiency of simple char
separators for now, but you will be ready for the day when someone wants "::"
as a separator - just add a new pattern type "double-colon-separated". You will
also be ready if/when there is a need for regexps or other more powerful
patterns. Finally you will have explicit annotations so you know which type of
separator is required on a per-prefix basis.
Also beware that you will need escape syntax for when the separator pattern is
not being used as a separator. We already see this in proton with Azure topic
names containing "/", which proton's URL parser treats as a URL separator. We
need to use URL hex escapes to work around this, dispatch will have the same
problem and need a similar solution.
> Prefix delimiters: allow slashes as well as periods
> ----------------------------------------------------
>
> Key: DISPATCH-286
> URL: https://issues.apache.org/jira/browse/DISPATCH-286
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Router Node
> Reporter: Ted Ross
> Assignee: Ted Ross
> Fix For: 0.6
>
>
> In 0.6.0-beta2, the only delimiter character available for address prefixes
> is the "." character. It would be desirable to also allow slash (and
> possibly backslash) as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
