FreeRTOS-Kernel/FreeRTOS-Plus/Demo/coreMQTT_Windows_Simulator
andysun2015 426ad44c05
Remove using_mbedtls folder and move its content to the parent folder (#717)
Move the contents of FreeRTOS/FreeRTOS-Plus/Source/Application-Protocols/network_transport/using_mbedtls/
to its parent folder i.e. FreeRTOS/FreeRTOS-Plus/Source/Application-Protocols/network_transport/.
This removes one unnecessary folder in the hierarchy.
2021-11-18 13:23:41 -08:00
..
Common [AUTO][RELEASE]: Bump file header version to "202111.00" 2021-11-13 02:37:14 +00:00
MQTT_Basic_TLS Remove using_mbedtls folder and move its content to the parent folder (#717) 2021-11-18 13:23:41 -08:00
MQTT_Keep_Alive Remove using_mbedtls folder and move its content to the parent folder (#717) 2021-11-18 13:23:41 -08:00
MQTT_Multitask Remove using_mbedtls folder and move its content to the parent folder (#717) 2021-11-18 13:23:41 -08:00
MQTT_Mutual_Auth Remove using_mbedtls folder and move its content to the parent folder (#717) 2021-11-18 13:23:41 -08:00
MQTT_Mutual_Auth_wolfSSL Remove using_mbedtls folder and move its content to the parent folder (#717) 2021-11-18 13:23:41 -08:00
MQTT_Plain_Text Remove using_mbedtls folder and move its content to the parent folder (#717) 2021-11-18 13:23:41 -08:00
MQTT_Serializer [AUTO][RELEASE]: Bump file header version to "202111.00" 2021-11-13 02:37:14 +00:00
readme.txt Multiple tidy up and corrections preparing for release (#390) 2020-11-09 14:50:33 -08:00
readme_also_coreMQTT_multithreading_agent.url Add links to the MQTT agent in the non-agent mqtt demos (#470) 2020-12-11 21:12:44 -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.