mirror of
https://github.com/FreeRTOS/FreeRTOS-Kernel.git
synced 2025-10-15 17:27:46 -04:00
c0d4c7c67c
The MQTT library has been updated with the MQTT_RECV_POLLING_TIMEOUT_MS and MQTT_SEND_RETRY_TIMEOUT_MS configurations which should be set to zero when using a dummy timer function to avoid possibility of infinite loop when retrying failed transport send/receive calls. As the MQTT Keep Alive demo uses a dummy timer function, this PR updates the demo configuration to set these timeouts to zero. |
||
|---|---|---|
| .. | ||
| Common | ||
| MQTT_Basic_TLS | ||
| MQTT_Keep_Alive | ||
| MQTT_Multitask | ||
| MQTT_Mutual_Auth | ||
| MQTT_Plain_Text | ||
| MQTT_Serializer | ||
| readme.txt | ||
| readme_coreMQTT.url | ||
The subdirectories of this directory contain multiple examples that demonstrate coreMQTT using in both single and multi-threaded scenarios, as well as with both plain text and authenticated and encrypted network interfaces. The multi threaded example creates an MQTT agent (or daemon task). It is thread safe because only the agent task is allowed to access the coreMQTT API - hence the API is only accessed from one FreeRTOS task. Other tasks and interrupts needing to interact with the MQTT agent do so through a thread safe queue. We are generalising this technique for future coreMQTT releases, which will have a re-usable agent component. ! Plain text examples are for ease of evaluation only - product devices should ! always use authenticated and encrypted communication. Never send private or ! sensitive data on an unencrypted connection.