rtpengine

Commit Graph

Author	SHA1	Message	Date
Donat Zenichev	423d7bf824	MT#59086 Unify header files. In the header files follow the rules: 1. Firstly goes ifndef/define construction, then one empty row. 2. Secondly go system headers, so in angle-brackets, then one empty row. 3. If there are important pre-processor definitions, which affect the following custom file headers, they are added next, then one empty row. 4. Thirdly custom header files, so in double quotes, then at least one empty row. 5. If there is "xt_RTPENGINE.h", it's mentioned next, but separately, then one empty row. 6. Then pre-processor definitions, and one empty row before the code. In some situations it's allowed to step aside from the rules, when inclusions are dependent on each other, so on specific sequence, and also possibly on some inline objects definitions. But, if possible to follow the rules, it should be done. Change-Id: I6bec69b508653947c04e7785775373d21112eb58	2 years ago
Richard Fuchs	2975b2131d	MT#55283 convert struct call to typedef Change-Id: I1f01fdf74d6d3952413ebc02dfdb9770b324481c	2 years ago
Richard Fuchs	64d7a12701	MT#55283 add new `summary` mqtt option Change-Id: I7e4a2327f6aca2c73349b3ae02d4184460575e89	3 years ago
Richard Fuchs	c56c3cff4d	MT#55283 refactor MQTT callbacks Use dedicated functions and different code paths for the different use cases, instead of just a single function which does if/else all the time. Change-Id: Ic3ab928c3605cfe4a2f48889e95a3a1ddccdbbec	3 years ago
Richard Fuchs	369e64f9a7	TT#14008 add mqtt support Change-Id: Ica4a3e4ef58eadf3feca44ea63f2308103b3146f	5 years ago

5 Commits (1eb0c5e13e74c589fb4069ae7aff4908fec2b800)