Browsing Italian translation

110 of 20 results
MQ Telemetry Transport
(no translation yet)
Located in mqtt.7.xml:13(refpurpose)
<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)
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"></uri>.
(no translation yet)
Located in mqtt.7.xml:27(para)
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)
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)
Clients can receive messages by creating subscriptions. A subscription may be to an explicit topic, in which case only messages to that topic will be received, or it may include wildcards. Two wildcards are available, <option>+</option> or <option>#</option>.
(no translation yet)
Located in mqtt.7.xml:59(para)
<option>+</option> can be used as a wildcard for a single level of hierarchy. It could be used with the topic above to get information on all computers and hard drives as follows:
(no translation yet)
Located in mqtt.7.xml:63(para)
As another example, for a topic of "a/b/c/d", the following example subscriptions will match:
(no translation yet)
Located in mqtt.7.xml:69(para)
<option>#</option> can be used as a wildcard for all remaining levels of hierarchy. This means that it must be the final character in a subscription. With a topic of "a/b/c/d", the following example subscriptions will match:
(no translation yet)
Located in mqtt.7.xml:84(para)
mqtt defines three levels of Quality of Service (QoS). The QoS defines how hard the broker/client will try to ensure that a message is received. Messages may be sent at any QoS level, and clients may attempt to subscribe to topics at any QoS level. This means that the client chooses the maximum QoS it will receive. For example, if a message is published at QoS 2 and a client is subscribed with QoS 0, the message will be delivered to that client with QoS 0. If a second client is also subscribed to the same topic, but with QoS 2, then it will receive the same message but with QoS 2. For a second example, if a client is subscribed with QoS 2 and a message is published on QoS 0, the client will receive it on QoS 0.
(no translation yet)
Located in mqtt.7.xml:100(para)
110 of 20 results

No translation group has been assigned.

You are not logged in. Please log in to work on translations.

Contributors to this translation: Guybrush88, Loris Turchetti.