> Destination Name Syntax
> TIBCO Enterprise Message Service places few restrictions on the syntax and interpretation of destination names. System designers and developers have the freedom to establish their own conventions when creating destination names. The best destination names reflect the structure of the data in the application itself.
> Structure
> A destination name is a string divided into elements, each element separated by the dot character (.). The dot character allows you to create multi-part destination names that categorize destinations.
> Empty strings ("") are not permitted destination names. Likewise, elements cannot incorporate the dot character by using an escape sequence.
> Although they are not prohibited, we recommend that you do not use tabs, spaces, or any unprintable character in a destination name. You may, however, use wildcards. See Wildcards for more information.
> Length
> Destinations are limited to a total length of 249 characters. However, some of that length is reserved for internal use. The amount of space reserved for internal use varies according to the number of elements in the destination; destinations that include the maximum number of elements are limited to 196 characters.
> A destination can have up to 64 elements. Elements cannot exceed 127 characters. Dot separators are not included in element length.
> Destination Name Performance Considerations
> When designing destination naming conventions, remember these performance considerations:

> ● | Shorter destination names perform better than long destination names.

> ● | Destinations with several short elements perform better than one long element.

> ● | A set of destinations that differ early in their element lists perform better than subjects that differ only in the last element.

> Special Characters in Destination Names
> These characters have special meanings when used in destination names:

> Table 9 Characters with Special Meaning in Destination Names
> Char | Char Name | Special Meaning
> _ | Underscore | Destination names beginning with underscore are reserved. It is illegal for application programs to send destinations with underscore as the first character of the first element, except _INBOX. It is legal to use underscore elsewhere in destination names.
> . | Dot | Separates elements within a destination name.
> > | Greater-than | Wildcard character, matches one or more trailing elements.
> * | Asterisk | Wildcard character, matches one element.

> For more information on wildcard matching, see Wildcards * and >.
> Examples
> These examples illustrate the syntax for destination names.

> Table 10 Valid Destination Name Examples
> NEWS.LOCAL.POLITICS.CITY_COUNCIL
> NEWS.NATIONAL.ARTS.MOVIES.REVIEWS
> CHAT.MRKTG.NEW_PRODUCTS
> CHAT.DEVELOPMENT.BIG_PROJECT.DESIGN
> News.Sports.Baseball
> finance
> This.long.subject_name.is.valid.even.though.quite.uninformative

> Table 11 Invalid Destination Name Examples
> News..Natural_Disasters.Flood (null element)
> WRONG. (null element)
> .TRIPLE.WRONG.. (three null elements)
> News.Tennis.Stats.Roger\.Federer (backslash in the element Roger will be included in the element name, and will not escape the dot)

Copyright © TIBCO Software Inc. All Rights Reserved.