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 I checked "yes, UDP" and "other".
Over a decade ago I wrote a variant of tftp that could handle demultiplexing multiple streams from the same port, which is something tftp doesn't handle with any official extensions I'm aware of. For very weird procedural reasons my software was only allocated 8 local ports and needed to handle 40 concurrent tftp transfers.
Right now I'm working on a remote rendering AR solution that uses UDP/QUIC with porotobuf payloads for video streaming plus all the synchronization and health data the system needs.