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)
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)
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 for a project where I needed to stream and re-embed virtual framebuffers and commands into a sort of encoding / streaming / rendering farm.
it started just piping things through socat over raw udp, and having a sidecar message queue, but we needed to eventually add some metadata on top of the stream for timestamps, sequences, and some encoding hints into "frames".
it was a wonky enough and deeply integrated setup that nothing normal quite fit the bill.