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 .

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)

@b0rk things I've built with UDP:

- a lot of bespoke lighting systems based on ESP8266 modules, where I couldn't be bothered to write a proper ArtNet interface

- a system for doing reactive backlighting on large projector screens, similar to Philips Ambilight but on a full event stage scale

- a silly network buffer storage system where you "store" stuff by repeatedly forwarding packets

- some basic P2P stuff

- a few toy VoIP systems

- a few attempts at multiplayer game code along the years

@b0rk also, if it counts, I've written interfaces to other people's custom UDP protocols, both for personal reasons and at work. Pioneer Rekordbox (DJ software) has some custom UDP stuff for timecode and OSC and I tinkered with that for a bit.

I see custom UDP stuff a lot in industrial control systems where it's easier to deal with protocol-level retries and acknowledgement in exchange for stateless multicast/broadcast capability than it is to deal with stateful unicast, for various reasons.

@gsuberland @b0rk yep, at my old employer we had designed a custom UDP protocol for talking to our DALI light control devices. It's easier to implement a simple UDP via multicast where the recipient just sends back an acknowledgement packet, especially if you want to connect to devices where physical access is difficult (stuff built in the ceiling for example) and have a "backdoor" when the customer messes up their config.