I suppose a way to paraphrase this question is why can’t HTTP just use UDP? What specific functionalities provided by the TCP are explicitly required by HTTP?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I suppose a way to paraphrase this question is why can’t HTTP just use UDP? What specific functionalities provided by the TCP are explicitly required by HTTP?
Ordering, non-duplication, integrity, pacing of large payloads, … same as anybody else needs really. There was a move some years back to provide HTTP over UDP for tiny payloads that would fit into a single datagram, and ditto the responses, but most HTTP payloads are too big for one datagram so the point is lost.