FreeRTOS-Kernel/FreeRTOS-Plus/Demo/coreMQTT_Windows_Simulator
RichardBarry 596b466300
Add code comments on the different requirements for credential constants between evaluation and production systems. (#386)
Only comments have changed.  No code changes.

Co-authored-by: Cobus van Eeden <35851496+cobusve@users.noreply.github.com>
Co-authored-by: Gary Wicker <14828980+gkwicker@users.noreply.github.com>
2020-11-09 14:56:52 -08:00
..
Common Multiple tidy up and corrections preparing for release (#390) 2020-11-09 14:50:33 -08:00
MQTT_Basic_TLS Add code comments on the different requirements for credential constants between evaluation and production systems. (#386) 2020-11-09 14:56:52 -08:00
MQTT_Keep_Alive Add code comments on the different requirements for credential constants between evaluation and production systems. (#386) 2020-11-09 14:56:52 -08:00
MQTT_Multitask Add code comments on the different requirements for credential constants between evaluation and production systems. (#386) 2020-11-09 14:56:52 -08:00
MQTT_Mutual_Auth Add code comments on the different requirements for credential constants between evaluation and production systems. (#386) 2020-11-09 14:56:52 -08:00
MQTT_Plain_Text Add code comments on the different requirements for credential constants between evaluation and production systems. (#386) 2020-11-09 14:56:52 -08:00
MQTT_Serializer Add code comments on the different requirements for credential constants between evaluation and production systems. (#386) 2020-11-09 14:56:52 -08:00
readme.txt Multiple tidy up and corrections preparing for release (#390) 2020-11-09 14:50:33 -08:00
readme_coreMQTT.url Multiple tidy up and corrections preparing for release (#390) 2020-11-09 14:50:33 -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.