FreeRTOS-Kernel/FreeRTOS-Plus/Demo/coreMQTT_Windows_Simulator
Archit Aggarwal 682447445b
Bump backoffAlgorithm submodule for API change and update demos (#426)
The API of FreeRTOS/backoffAlgorithm library has changed to remove dependency on random number generator; instead require the caller to generate the random number and pass it to the BackoffAlgorithm_GetNextBackoff API for backoff period calculation. This PR updates the submodule pointer commit, and updates the demos and tests to use the simplied library API
2020-11-30 11:12:07 -08:00
..
Common Multiple tidy up and corrections preparing for release (#390) 2020-11-09 14:50:33 -08:00
MQTT_Basic_TLS Bump backoffAlgorithm submodule for API change and update demos (#426) 2020-11-30 11:12:07 -08:00
MQTT_Keep_Alive Bump backoffAlgorithm submodule for API change and update demos (#426) 2020-11-30 11:12:07 -08:00
MQTT_Multitask Bump backoffAlgorithm submodule for API change and update demos (#426) 2020-11-30 11:12:07 -08:00
MQTT_Mutual_Auth Bump backoffAlgorithm submodule for API change and update demos (#426) 2020-11-30 11:12:07 -08:00
MQTT_Plain_Text Bump backoffAlgorithm submodule for API change and update demos (#426) 2020-11-30 11:12:07 -08:00
MQTT_Serializer Bump backoffAlgorithm submodule for API change and update demos (#426) 2020-11-30 11:12:07 -08:00
readme.txt Multiple tidy up and corrections preparing for release (#390) 2020-11-09 14:50:33 -08:00
readme_coreMQTT.url Update urls in code to those on the server (#396) 2020-11-10 10:53:14 -08:00

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.