Henrik Maier

I like also like to add to the discussion the fact that a message can only be removed from the queue if sufficient memory has been allocated. So one needs...

Are there any updates on this review? It is a very simple change and would make mqtt usage much easier and more memory efficient as we can optimise the memory...

Ok, I accept that you stay by your convention. Would you accept a PR for such an API call?

@TiejunMS Yes, that would be a workaround, thank you for the suggestion. But I rather like to see that in an official API than accessing internal data structured directly. Compared...

Unfortunately we have to support vanilla MQTT and digest arbitrary sized messages. So sensible and adaptive buffer sizing is important, we are on an embedded device and memory is finite....

Hello @TiejunMS, here is a first implementation of a `_nxd_mqtt_client_message_length_get()` function to retrieve topic length and message length: ``` UINT _nxd_mqtt_client_message_length_get(NXD_MQTT_CLIENT *client_ptr, UINT *topic_length_ptr, UINT *message_length_ptr) { UINT status; NX_PACKET...

@TiejunMS Thanks and sure I keep in the mean time my private extension. While dealing with the memory allocation and the packet queue I also noticed one other potential issue...

Ordinary TCP/UDP packets can simply be released if they don't comply by content or size. The TLS protects only between device and broker. MQTT data can travel between brokers and...

If the pointer constness differ, then either there is either a warning when assigning to `p_context` or a warning when using `p_context` in the callback function. This would be _"initialization...

Great. The approach to change it for v4.0 makes sense,