[OASIS Issue Tracker] (MQTT-245) Remove trailing slashes from topic strings (review comment from Nicholas Humfrey)

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/MQTT-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43661#comment-43661 ] 

Rick Bullotta commented on MQTT-245:
------------------------------------

I agree with Nicholas that this type of topic format should be explicitly forbidden and rejected by brokers.

> Remove trailing slashes from topic strings (review comment from Nicholas Humfrey)
> ---------------------------------------------------------------------------------
>
>                 Key: MQTT-245
>                 URL: https://issues.oasis-open.org/browse/MQTT-245
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.1.1
>            Reporter: Richard Coppen
>
> Public review comment received from Nicholas Humfrey (point 8) 
> 8) I do wish that leading and trailing slashes were forbidden. I think 
> topic names should either have structure and semantic meaning, or not. 
> The half-way house of 'use the topic name however you want' and slashes 
> being significant for pattern-matching is confusing.
> Roger Light has responded this comment as follows:
> Not that I'm disagreeing with you, but the leading/trailing slashes
> just create zero length topic hierarchy element at the beginning/end
> of the topic. So the topic "/mqtt//comment/" would be split into five
> levels, '', 'mqtt', '', 'comment' and ''. The only inconsistency that
> I am aware of is that although leading slashes allow you to produce a
> topic that starts with a zero length element, there is no way to
> address that zero length element itself because zero length topics are
> forbidden for some reason.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)