> If you are dropping packets and losing data, why would it matter if you're making one request or several?
Let's just focus on the second part: why would it matter if you're making one request or several?
Because people make bad assumptions about the order that requests complete in, don't check that previous requests completed successfully, maybe don't know how (or care) because that's all buried in some frontend framework... maybe that's the point!
> Believing that one request maps to one packet is a frequent "gotcha" I have to point out to new network devs.
What is a "network dev"? Unless they're using UDP... maybe you're thinking of DNS? Nah probably not. QUIC? Is that the entire internet for you? Oh. What about encryption? That takes whole handshakes.
Send one packet, recipient always receives one packet, is a "gotcha" I have to point out to experienced network administrators... along with DNS requires TCP as well as UDP these days, what with DNSSEC, attack mitigations, etc.