- 09 Jun, 2020 1 commit
-
-
Nathaniel Wesley Filardo authored
* mqtt: expose "connfail" callback via :on() This makes it just like all the other callbacks in the module and is a revision of behavior called out in https://github.com/nodemcu/nodemcu-firmware/pull/2967 * mqtt: clarify when puback callback fires * mqtt: Don't reference stack buffers from the heap The confusingly-named "mqtt_connection_t" object is just a triple of - a serialized mqtt message pointer and length - a buffer pointer (to which the above can be written) - a message identifier The last of these must be passed around the mqtt state machine, but the first two are very local and the buffer is always sourced from the C stack. Unfortunately, because the entire structure is persisted in the heap, some callers assume that they can always use the structure without reinitialization (see mqtt_socket_close), which will trash the C stack. Sever the pairing between message id and local state, punt the local state entirely out of the heap, and rename things to be less confusing.
-
- 21 Jul, 2019 1 commit
-
-
Johny Mattsson authored
The PR removed the bulk of non-newlib headers from the NodeMCU source base. app/libc has now been cut down to the bare minimum overrides to shadow the corresponding functions in the SDK's libc. The old c_xyz.h headerfiles have been nuked in favour of the standard <xyz.h> headers, with a few exceptions over in sdk-overrides. Again, shipping a libc.a without headers is a terrible thing to do. We're still living on a prayer that libc was configured the same was as a default-configured xtensa gcc toolchain assumes it is. That part I cannot do anything about, unfortunately, but it's no worse than it has been before. This enables our source files to compile successfully using the standard header files, and use the typical malloc()/calloc()/realloc()/free(), the strwhatever()s and memwhatever()s. These end up, through macro and linker magic, mapped to the appropriate SDK or ROM functions.
-
- 17 Feb, 2019 1 commit
-
-
sergio authored
-
- 30 Nov, 2018 1 commit
-
-
Johan Ström authored
* MQTT: handle large/chunked/fragmented messages properly If a message spans multiple TCP packets it must be buffered before delivered to LUA. Prior code did not do this at all, so this "patch" really adds proper handling of fragmented MQTT packets. This could also occur if multiple small messages was sent in a single TCP packet, and the last message did not completely fit in that packet. Introduces a new option to the mqtt.Client constructor: max_publish_length which defaults to 1024 Introduces a new 'overflow' callback. Fixes issue #2308 and proper fix for PR #2544. * mqtt.md: clarified heap allocation * mqtt: ensure ack is sent for overflowed publish If QoS is used we should still acknowledge that we received it, or server might retransmit it later.
-
- 19 Apr, 2017 1 commit
-
-
Nathaniel Wesley Filardo authored
Partially addresses nodemcu/nodemcu-firmware#1773.
-
- 20 Mar, 2016 1 commit
-
-
philip authored
-
- 10 Mar, 2016 1 commit
-
-
philip authored
-
- 29 Mar, 2015 1 commit
-
-
funshine authored
-
- 31 Jan, 2015 1 commit
-
-
Tuan PM authored
-
- 23 Jan, 2015 1 commit
-
-
funshine authored
-