3 ms·
> It was HTTP/1 that was decidedly stateless. And this was a principled stance. HTTP/1 was for serving web pages, and web pages are documents. Then we started
by taneq 3y ago
> It was HTTP/1 that was decidedly stateless.
And this was a principled stance. HTTP/1 was for serving web pages, and web pages are documents. Then we started generating web pages from databases, which was pretty useful, but also started the slippery slope to us hijacking the web and turning it into a network of applications running on a nested operating system.
- ignoramous 3y ago> ...the slippery slope to us hijacking the web and turning it into a network of applications running on a nested operating system. Well if folks drop anything that's not 53, 443, or 80, then what other choices are left?
- taneq 3y agoThat's a slightly different question (ie. how do we pragmatically tunnel our data between applications) but yes, that evolutionary race to the bottom (or port 80/443 as you say) also sucks.