There have not been any changes in the scheduling logic since we doubled the time-before-tx on March 10 2016 (1bb19bf818
). After reading the discussion here (and on Twitter) I just added another 200ms (c8bd97b135
) to increase support for slow connections (or slow gateways). I’ll try to have that change deployed later today.
This is definitely not true. In the future we may give application owners the option to prefer authenticated/secure gateways (using MQTT or gRPC over TLS) over unauthenticated/insecure gateways (using JSON over UDP), but that won’t be enabled by default.
The MQTT server in between indeed adds a bit of delay. We’re working hard on reducing this by optimizing our MQTT server. Right now the extra delay is a few milliseconds at worst.
Of course TCP may also add some extra delay on bad connections (TCP packets are retransmitted, whereas UDP packets would simply get lost)