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 Many years ago for fun I used UDP multicast on a LAN to signal multiple computers. They all ran a little Java program that would beep the PC speaker to try to play a polyphonic melody together.
It was just a crazy project just to play with multicast, and would quickly get out of sync (no major attempt was made to correct for that).
IIRC the packets were mostly for timing, they didn’t contain the melody.
Also learned a lot thunking to 16 bit Windows PC speaker calls from Java too.