FreeRTOS-Kernel/FreeRTOS-Plus/Demo/coreMQTT_Windows_Simulator
Archit Aggarwal 21878bd619
Allow overriding default definitions of logging macros (#384)
* Update logging_stack.h file to avoid use of __FUNCTION__ macro

* Revert to use __FUNCTION__ instead of __FILE__

* Fix comment about metadata format

* Fix incorrect mapping of SdkLog function

* Fix typo causing LOG_METADATA_ARGS to be undefined

* Fix another bug with SdkLog macro definition

* Fix formatting

* Move mapping of SdkLog to vLoggingPrintf from logging_stack to config files

* Remove dependency of LIBRARY_LOG_NAME on LIBRARY_METADATA_* macros

* Minor improvements

Co-authored-by: Gary Wicker <14828980+gkwicker@users.noreply.github.com>
Co-authored-by: RichardBarry <3073890+RichardBarry@users.noreply.github.com>
2020-11-09 15:07:19 -08:00
..
Common Multiple tidy up and corrections preparing for release (#390) 2020-11-09 14:50:33 -08:00
MQTT_Basic_TLS Allow overriding default definitions of logging macros (#384) 2020-11-09 15:07:19 -08:00
MQTT_Keep_Alive Allow overriding default definitions of logging macros (#384) 2020-11-09 15:07:19 -08:00
MQTT_Multitask Allow overriding default definitions of logging macros (#384) 2020-11-09 15:07:19 -08:00
MQTT_Mutual_Auth Allow overriding default definitions of logging macros (#384) 2020-11-09 15:07:19 -08:00
MQTT_Plain_Text Allow overriding default definitions of logging macros (#384) 2020-11-09 15:07:19 -08:00
MQTT_Serializer Allow overriding default definitions of logging macros (#384) 2020-11-09 15:07:19 -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.