when I asked people to explain how UDP works I got a lot of answers to the effect of "it's spray and pray"

but I'm having trouble thinking of examples of UDP-based protocols that actually work in a "spray and pray" way —

* DNS is "send 1 packet, retry if you don't get a reply”
* QUIC is a sophisticated system for streaming data over UDP
* I'd guess that video protocols correct for packet loss
* maybe statsd is a "spray and pray” system?

(please do not reply to this explaining how UDP works)

@b0rk I think that's the difference between raw UDP and protocols built on top of UDP
@RandomDamage I said "please do not reply to this explaining how UDP works" for a reason, I just want answers to the specific question I asked

@b0rk sorry.

Can I offer VOIP as a place where it is also used in "spray and pray" mode?

The actual use cases are very limited, but the place to look is anywhere that latency dominates the requirements

@RandomDamage @b0rk Is VOIP actually "spray and pray"?

I think it helps to define what "spray and pray" means, and I'd say it means sending out packets without any feedback.

Request/response is not spray and pray, TCP style reliable in-order delivery is not, but also anything which does congestion control also wouldn't be considered spray and pray.

AFAIK, VOIP is generally done over RTP which does have packet loss detection and congestion control.