3 ms·
Why add the additional complexity of multiple connection points? Protocols support both of those operations perfectly well and it seems that adding URLs would j
by eikenberry 3y ago
Why add the additional complexity of multiple connection points? Protocols support both of those operations perfectly well and it seems that adding URLs would just confuse things.
- liquidgecka 3y agoBecause at some point you will need to deprecate ciphers and when you do you don't want old clients to explode. The domain is the way you version connection requirements so you can support old clients with crappy ssl options without screwing up the security of new clients.
- nine_k 3y agoSometimes all you got is port 443, and adding subdomains is a non-zero hassle, especially if you serve all off the APIs from the same code anyway.
- eikenberry 3y agoYou don't need subdomains or other ports because you encapsulate everything in the protocol. A system that works on a protocol only really needs a data socket which can be simulated pretty easily via any URL with the POSTs working as a bursty stream.
- kiitos 3y agoHTTP is itself a protocol, and URLs are part of that protocol. They're not really "connection points" in any meaningful sense.