3 ms·
UDP and TCP aren't comparable to HTTP. HTTP is an application layer protocol, which rides on top of UDP and TCP, which are transport layer protocols. Be caref
by iamwil 18y ago
UDP and TCP aren't comparable to HTTP. HTTP is an application layer protocol, which rides on top of UDP and TCP, which are transport layer protocols.
Be careful when you get carried away.
- moe 18y agoRead my sentence again, I wrote: UDP is commonly used here because even the TCP latency is too much. I meant to say: They not only avoid HTTP - they even avoid TCP, too. Well, the phrasing was not ideal, I'll give you that.
- Gonsalu 18y agohttp://www.w3.org/Protocols/rfc2616/rfc2616-sec1.html#sec1.4 http://www.w3.org/Protocols/rfc2616/rfc2616-sec1.html#sec1.4 "HTTP only presumes a reliable transport; any protocol that provides such guarantees can be used" UDP does not guarantee packet delivery, thus HTTP cannot ride on top of UDP.
- jacquesm 18y agoI think that entry should have read 'http only presumes a reliable connection based transport'. It would be pretty hard to make http work over something that guarantees transport of a packet but is not connection oriented.
- iamwil 18y agoI stand corrected on that point.
- axod 18y agoUDP [ Reliable_protocol_wrapper [ HTTP ] ] Where Reliable_protocol_wrapper does retransmissions, acks, sequence numbering etc. There's no reason why you couldn't use HTTP over UDP if you like, I'm sure it's most likely been done in the past - if only just for fun.
- deleted 18y ago[deleted]
- abstractbill 18y agoActually it can, and does: http://en.wikipedia.org/wiki/HTTPU http://en.wikipedia.org/wiki/HTTPU
- Gonsalu 18y agoHTTPU is not HTTP. That's why it has a different name...