3 ms·
In the 90s it was commonplace to design a new protocol on top of TCP/IP. These days, all the tooling and infrastructure is for HTTP. Designing a new protocol, y
by bitwize 3y ago
In the 90s it was commonplace to design a new protocol on top of TCP/IP. These days, all the tooling and infrastructure is for HTTP. Designing a new protocol, you'd be starting from scratch; HTTP is much, much easier to build an application on top of.
- unilynx 3y agoI doubt QUIC is easier than TCP to build on. But it's much easier to get your new protocol through firewalls and other middleware when using port 443 than trying to introduce a new port (or worse: a new protocol number)
- tengwar2 3y agoWhich sounds like more of a disadvantage if you are running a firewall.
- anticensor 3y agoIf your firewall drops unknown protocols, then it is broken. Internet is designed to be default-open, not default-closed.