OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (MQTT-233) Modify Language around use of $ topics

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

Richard Coppen commented on MQTT-233:

Discussed on TC call 29.05.2014 and moved to futures component.
The $ topic domain has been discussed a number of times by the TC. The thread was started initially as part of MQTT-16 which defined much of the current wording. The intention was to avoid future application migration problems while recognizing current server implementations use the $ prefix as a home for topics with special meaning. The TC will continue the conversation separately to progressing 3.1.1 

> Modify Language around use of $ topics
> --------------------------------------
>                 Key: MQTT-233
>                 URL: https://tools.oasis-open.org/issues/browse/MQTT-233
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: futures
>    Affects Versions: 3.1.1
>         Environment: All
>            Reporter: Marco Carrer
>            Priority: Critical
> Section 4.7.2 Topics beginning with $ states 'The Server SHOULD prevent Clients from using such (where 'such' means topics beginning with $) Topic Names to exchange messages with other Clients'.  We think this is a bit restrictive and should not necessarily be strictly enforced by the broker.  
> Instead we would prefer the 'SHOULD' be changed to a 'MAY'. This is consistent with the Non normative comment which states that "Applications cannot use a topic with a leading $ character for their own purposes".
> We would prefer a language that leads broker implementations to may allow the use of $ topic namespaces through configurable options rather block such topics in an hard-coded way.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]