Nick,
On 12/11/2012 16:09, Nicholas Wright wrote:
> On 12/11/2012 15:48, Nigel Deakin wrote:
>> I would therefore like to suggest that we specify that the following characters must always be valid in a durable or
>> non-durable subscription name:
>>
>> * Java letter or digit (as defined in Character.isLetterOrDigit)
>>
>> * Underscore (_, or \u005f)
>
> This looks like standard practice to me. Many people also use '.' in their naming strategy. Given that this is a
> convention I see being used widely can we include this also please.
>
> The choice of only underscores or alphanumerics would not break the Apache ActiveMQ implementation to my knowledge
> (Rob is likely better placed to act as the authority on this). They have a wildcarding mechanism for subscription to
> destinations which takes things like '*', this code will need to be checked. But this is a value add feature outside
> of the spec.
I know some JMS providers make use of "." and "*" in destination names for wildcarding. But I'm only concerned with
subscription names here. Do your comments apply to subscription names as well?
Nigel