3 ms·
I'll give a potentially flamebaity response... But it's because reality appears to say that OSI protocols were right and TCP was wrong. Plain TCP essentially e
by p_l 8y ago
I'll give a potentially flamebaity response... But it's because reality appears to say that OSI protocols were right and TCP was wrong.
Plain TCP essentially emulates a full duplex serial port. Applications need more on top of that. Methods for framing, attaching Metadata, data flows, secure transport layers, etc.
So HTTP which provides a modicum of those options ends up being default, because it's available.
For comparison, OSI defined various components to handle those elements and a proper OSI stack should have then available to application developer.
Another example would be Symbolics Lisp Machines (Genera) where the network layer provided a bunch of mid-layer protocols, like one which provided messages that were formed of basic typed data structures. So people would use those to quickly build custom protocols for their applications, thanks to not having to deal with low level details.
Various Middleware also come to mind.
TCP is not enough.