From d2b697a04e571751699066dc4784396e2bbd0e39 Mon Sep 17 00:00:00 2001 From: Faith Hunja Date: Sat, 12 Jun 2021 01:48:04 +0300 Subject: [PATCH 1/2] Updated README.md (#70) * Fixed grammatical error * Fixed grammatical error * Fixed some grammatical errors * Updated README.md * Updated README.md * Updated README.md Updated the changes according to the reviews * Update README.md * Grammar fixes * Updated README.md Co-authored-by: Jim Bennett --- 1-getting-started/lessons/4-connect-internet/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/1-getting-started/lessons/4-connect-internet/README.md b/1-getting-started/lessons/4-connect-internet/README.md index c6dcdf4e..49ae2dbe 100644 --- a/1-getting-started/lessons/4-connect-internet/README.md +++ b/1-getting-started/lessons/4-connect-internet/README.md @@ -76,9 +76,9 @@ Follow the relevant step below to connect your device to the MQTT broker: ### A deeper dive into MQTT -Topics can have a hierarchy, and clients can subscribe to different levels of the hierarchy using wildcards. For example, you can send temperature telemetry messages to `/telemetry/temperature` and humidity messages to `/telemetry/humidity`, then in your cloud app subscribe to `/telemetry/*` to receive both the temperature and humidity telemetry messages. +Topics can have a hierarchy, and clients can subscribe to different levels of the hierarchy using wildcards. For example, you can send temperature telemetry messages to the `/telemetry/temperature` topic and humidity messages to the `/telemetry/humidity` topic, then in your cloud app subscribe to the `/telemetry/*` topic to receive both the temperature and humidity telemetry messages. -Messages can be sent with a quality of service (QoS), which determines the guarantees of the message being received. +Messages can be sent with a quality of service (QoS), which determines the guarantee of the message being received. * At most once - the message is sent only once and the client and broker take no additional steps to acknowledge delivery (fire and forget). * At least once - the message is re-tried by the sender multiple times until acknowledgement is received (acknowledged delivery). @@ -86,11 +86,11 @@ Messages can be sent with a quality of service (QoS), which determines the guara ✅ What situations might require an assured delivery message over a fire and forget message? -Although the name is Message Queueing, it doesn't actually support message queues. This means that if a client disconnects, then reconnects it won't receive messages sent during the disconnection except for those messages that it had already started to process using the QoS process. Messages can have a retained flag set on them. If this is set, the MQTT broker will store the last message sent on a topic with this flag, and send this to any clients who later subscribe to the topic. This way the clients will always get the latest message. +Although the name is Message Queueing (initials in MQTT), it doesn't actually support message queues. This means that if a client disconnects, then reconnects it won't receive messages sent during the disconnection, except for those messages that it had already started to process using the QoS process. Messages can have a retained flag set on them. If this is set, the MQTT broker will store the last message sent on a topic with this flag, and send this to any clients who later subscribe to the topic. This way, the clients will always get the latest message. MQTT also supports a keep alive function that checks to see if the connection is still alive during long gaps between messages. -> 🦟 [Mosquitto from the Eclipse Foundation](https://mosquitto.org) has a free MQTT broker you can run yourself to experiment with MQTT, along with a public MQTT broker you can use to test your code hosted at [test.mosquitto.org](https://test.mosquitto.org). +> 🦟 [Mosquitto from the Eclipse Foundation](https://mosquitto.org) has a free MQTT broker you can run yourself to experiment with MQTT, along with a public MQTT broker you can use to test your code, hosted at [test.mosquitto.org](https://test.mosquitto.org). MQTT connections can be public and open, or encrypted and secured using usernames and passwords, or certificates. From 28bd92acab474928a59b09d2fa3445beb8287cef Mon Sep 17 00:00:00 2001 From: Anurag Sharma <53372213+Anurag-0-1-A@users.noreply.github.com> Date: Sat, 12 Jun 2021 04:19:10 +0530 Subject: [PATCH 2/2] Creating README.hi.md (#69) Co-authored-by: Jim Bennett --- 1-getting-started/Translations/README.hi.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 1-getting-started/Translations/README.hi.md diff --git a/1-getting-started/Translations/README.hi.md b/1-getting-started/Translations/README.hi.md new file mode 100644 index 00000000..b0bf8623 --- /dev/null +++ b/1-getting-started/Translations/README.hi.md @@ -0,0 +1,16 @@ +# IoT . के साथ शुरुआत करना + +पाठ्यक्रम के इस भाग में, आपको इंटरनेट ऑफ थिंग्स से परिचित कराया जाएगा, और क्लाउड से कनेक्ट होने वाली अपनी पहली 'हैलो वर्ल्ड' IoT प्रोजेक्ट के निर्माण सहित बुनियादी अवधारणाओं को सीखेंगे। यह परियोजना एक रात की रोशनी है जो एक सेंसर ड्रॉप द्वारा मापे गए प्रकाश स्तर के रूप में रोशनी करती है। + +![WIO से जुड़ी LED प्रकाश के स्तर में परिवर्तन के साथ चालू और बंद होती है](https://github.com/microsoft/IoT-For-Beginners/blob/main/images/wio-running-assignment-1-1.gif?raw=true) + +## विषय + +1. [IoT का परिचय](lessons/1-introduction-to-iot/README.md) +1. [IoT में एक गहरा गोता](lessons/2-deeper-dive/README.md) +1. [सेंसर और एक्चुएटर्स के साथ भौतिक दुनिया के साथ बातचीत करें](lessons/3-sensors-and-actuators/README.md) +1. [अपने डिवाइस को इंटरनेट से कनेक्ट करें](lessons/4-connect-internet/README.md) + +## क्रेडिट + +सभी पाठ [जिम बेनेट](https://GitHub.com/JimBobBennett) द्वारा ♥️ के साथ लिखे गए थे