|
|
1.
|
|
|
mqtt
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mqtt.7.xml:7(refentrytitle) mqtt.7.xml:12(refname) mqtt.7.xml:18(command)
|
|
|
2.
|
|
|
7
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mqtt.7.xml:8(manvolnum)
|
|
|
3.
|
|
|
MQ Telemetry Transport
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mqtt.7.xml:13(refpurpose)
|
|
|
4.
|
|
|
Description
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mqtt.7.xml:23(title)
|
|
|
5.
|
|
|
<command>mqtt</command> is a publish/subscribe messaging protocol intended that is designed to be lightweight. It is useful for use with low power sensors, but is applicable to many scenarios.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mqtt.7.xml:24(para)
|
|
|
6.
|
|
|
This manual describes some of the features of mqtt version 3.1, to assist end users in getting the most out of it. For more complete information on mqtt, see <uri type="webpage">http://mqtt.org/</uri>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mqtt.7.xml:27(para)
|
|
|
7.
|
|
|
Publish/Subscribe
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mqtt.7.xml:34(title)
|
|
|
8.
|
|
|
The mqtt protocol is based on the principle of publishing messages and subscribing to topics, or "pub/sub". Multiple clients connect to a broker and subscribe to topics that they are interested in. Clients also connect to the broker and publish messages to topics. Many clients may subscribe to the same topics and do with the information as they please. The broker and mqtt act as a simple, common interface for everything to connect to. This means that you if you have clients that dump subscribed messages to a database, to twitter, pachube or even a simple text file, then it becomes very simple to add new sensors or other data input to a database, twitter or so on.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mqtt.7.xml:35(para)
|
|
|
9.
|
|
|
Topics/Subscriptions
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mqtt.7.xml:48(title)
|
|
|
10.
|
|
|
Messages in mqtt are published on topics. There is no need to configure a topic, publishing on it is enough. Topics are treated as a hierarchy, using a slash (/) as a separator. This allows sensible arrangement of common themes to be created, much in the same way as a filesystem. For example, multiple computers may all publish their hard drive temperature information on the following topic, with their own computer and hard drive name being replaced as appropriate:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mqtt.7.xml:49(para)
|
