len0rd/FreeRTOS-Kernel
1
0
Fork 0
mirror of https://github.com/FreeRTOS/FreeRTOS-Kernel.git synced 2025-10-14 16:57:41 -04:00
Code Issues Projects Releases Packages Wiki Activity
FreeRTOS-Kernel/FreeRTOS-Plus/Source/Application-Protocols
History
Oscar Michael Abrina 73b0d1b259
Support multiple transports in the same compilation unit (#434) 
By removing the definition of the NetworkContext struct in the header file, we allow the application to define it. This allows an application writer to use multiple transports in the same compilation unit. That way, multiple .c files do not have to be created for each transport.
2020-12-01 17:24:18 -08:00
..
coreHTTP@0882657628 Preparation for coreHTTP demos (#413) 2020-11-19 20:03:59 -05:00
coreMQTT@93c15bdab8 Update path to transport_interface.h from the coreMQTT submodule (#368) 2020-10-29 10:22:15 -07:00
network_transport Support multiple transports in the same compilation unit (#434) 2020-12-01 17:24:18 -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
ReadMe_network_transport.url Multiple tidy up and corrections preparing for release (#390) 2020-11-09 14:50:33 -08:00

readme.txt 

The 'core' branded application protocols are 'standalone' in that they do not
have any dependencies outside of the C library.  They use a simple transport
interface definition to ensure they are not dependent on the underlying TCP/IP
stack.  This directory collects together the application protocols that all use
the same transport interface definition (only coreMQTT at the time of writing,
soon to also include coreHTTP).

Directories:

+ coreMQTT contains the implementation of the coreMQTT library.  See:
  https://www.FreeRTOS.org/coremqtt

+ network_transport contains the transport interface definition.  See the
  comment above and https://www.freertos.org/transportinterface.html