Julia EvansJun 19, 2024

poll: have you ever designed a protocol that uses TCP or UDP directly? (vs using protocols that are based on TCP/UDP like DNS, HTTP, SSH, etc)

(you can pick more than one)

yes, TCP
36.1%
yes, UDP
24.3%
no, but I’ve used protocols based on them
37%
other
2.6%
Poll ended at .
Show threadJulia EvansJun 19, 2024

I'm so curious about what the 30% of you who are designing custom UDP-based protocols are doing, I would love to hear more!

(please only reply if you responded “yes, UDP” to the above poll)

Show threadbert hubert 🇺🇦🇪🇺🇺🇦Jun 19, 2024
@b0rk I used this once on an ESP8266 that converted pulses from an electrical power meter to UDP packets containing the number of pulses received so far. Using UDP (over WiFi) meant that the ESP8266 would never block, and because of the counter, missing a packet wasn't that much of a problem.
Show threadJulia EvansJun 19, 2024
@bert_hubert thank you that's a great example!
Show threadMatthew McPherrin

@b0rk @bert_hubert

I voted "yes udp" for a very similar microcontroller based project, though the opposite direction - LED 8-segment sign that you blasted UDP at to update. It was two-digit, so was just a single byte in a UDP packet. I didn't have a proper network stack at all, just an atmega with some ethernet adapter.

Jun 19, 2024 at 7:31pmWeb
Show threadRazJun 19, 2024
@mattm @b0rk @bert_hubert Another very similar case. But for 433MHz radios on an esp8266. Both sending and received packages were just raw UDP broadcasts with very small headers to keep it as simple as possible