[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (MQTT-60) Are topic strings normalized at all?
[ http://tools.oasis-open.org/issues/browse/MQTT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Coppen updated MQTT-60: ------------------------------- Fix Version/s: 3.1.1 Proposal: Answer: Topic names and topic filters are used in their literal form. Add "Topic level separators may appear adjacent in a Topic Filter or Topic Name to indicate a zero length topic level" as follows: Change Section 22.214.171.124 (WD 12) Lines 1298 - 1301 The forward slash ('/' 0x2F) is used to separate each level within a topic tree and provide a hierarchical structure to the topic names. The use of the topic level separator is significant when either of the two wildcard characters are encountered in topic filters specified by subscribing Clients. Topic level separators may appear anywhere in a Topic Filter or Topic Name. Adjacent Topic level separators indicate a zero length topic level. was:Topic names and topic filters are used in their literal form. > Are topic strings normalized at all? > ------------------------------------ > > Key: MQTT-60 > URL: http://tools.oasis-open.org/issues/browse/MQTT-60 > Project: OASIS Message Queuing Telemetry Transport (MQTT) TC > Issue Type: Improvement > Components: core > Affects Versions: 3.1.1 > Reporter: Allan Stockdill-Mander > Fix For: 3.1.1 > > > Should multiple adjacent topic level separators in a topic name being subscribed to/unsubscribed from be reduced to a single topic level separator. > Ie: is ////some////over/slashed///topic/etc/etc the same as /some/over/slashed/topic/etc/etc -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira