[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (MQTT-16) Reserve $SYS topic name
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
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 topic name be reserved?
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]