[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (MQTT-16) Reserve $SYS topic name
[ http://tools.oasis-open.org/issues/browse/MQTT-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Locke updated MQTT-16: ---------------------------- Proposal: 1. Applications MUST not define any topic names that start with a leading $ character 2. MQTT server implementations MAY define topic names that start with the the string "$SYS/" 3. MQTT server implementations MUST NOT define any other topics whose names start with a leading $ character. non-normative Examples: 1. A client that publishes or subscribes to $foo would be non-compliant 2. A server that defined and accepted subscriptions to $SYS/monitor/clients would be compliant 3. A server that defined and accepted publications to $SYS/control/setMaxClients would be compliant 4. A server that accepted subscriptions or publications on $foo would be non-compliant. 5. A topic name of stock/$price is compliant was: In normative document reserve the use of a top level topic for future use e.g. $SYS or $ADMIN In a non-normative document collect ideas and refine a topic space for administration. > Reserve $SYS topic name > ----------------------- > > Key: MQTT-16 > URL: http://tools.oasis-open.org/issues/browse/MQTT-16 > Project: OASIS Message Queuing Telemetry Transport (MQTT) TC > Issue Type: Improvement > Components: core > Affects Versions: 3.1.1 > Reporter: David Locke > Fix For: 3.1.1 > > > Many MQTT implementations today use $SYS as the head of a topic string for use in administration (configuration, operations, monitoring). > Can the $SYS or a similar topic name be reserved for future use ? As $SYS is already used by a number of servers using a different top level topic would avoid conflicts. > Would be good to collect ideas for a $SYS topic space. These ideas could initially go into a non-normative document but with potential for inclusion in a future spec. The intent being servers can implement some aspects of administration and monitoring in a consistent way > Some examples: > - Admin action like "unretain" a retained topic e.g. $SYS/topic/unretain (payload is the topic to unretain) > - Client wishes to query what subscriptions it has made e.g. $SYS/client/getsubs (topic is clientid) > - Client wishes to query how many messages are queued up awaiting delivery e.g. $SYS/client/getNoQueuedMessages > - Query the state of the MQTT server e.g. $SYS/server/getStatus > These examples should not be taken literally they are purely to show the type of things a $SYS topic space could be used for. -- 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]