3 ms·
What about when HTTP carries images? Or anything other than HyperText? And what is HyperText anyways? Why isn't it HTML Transport Protocol? Well, it's becau
by cryptonector 4y ago
What about when HTTP carries images? Or anything other than HyperText? And what is HyperText anyways? Why isn't it HTML Transport Protocol? Well, it's because HTML is not the only HyperText out there -- you can embed links in XML, XHTML, JSON, and all sorts of other things, as well as in HTTP headers.
HTTP isn't really only about HyperText, nor only about HTML -- it's about everything.
- Joker_vD 4y agoIt really should've been called GRRTP, Generic Request-Response Transfer Protocol, because there is nothing in it per se that's catered to hypertext transfer specifically. For comparison, look at FTP: it really is about the file transfer, you can tell that that is its application domain. Then look back at HTTP... yep, a generic request-response protocol, suitable for building pretty much anything else on top it.
- cryptonector 4y agoPretty much. But it is what it is, and it's too late to rename it now.