2 ms·
It's cleaner because you, in theory, can outsource an entire functionality class to your infrastructure. Less complexity for you to deal with. A bit like servi
by mseebach 16y ago
It's cleaner because you, in theory, can outsource an entire functionality class to your infrastructure. Less complexity for you to deal with.
A bit like serving static files - you put your files in a directory, and they're not only served, they're served faster, better and more reliably and scalable than whatever you can code as part of your app.
- tptacek 16y agoThe end to end argument suggests that stuffing things down into lower layers of the stack usually isn't cleaner.
- mseebach 16y agoI don't understand the end to end argument then? I'd say it's a huge win for cleanliness that I never need to touch a buffer in my life, but can still build and deploy high performance web apps, because I can build on the Apaches/nginx/whatevers of the world. Requiring users to log in in modern web stacks is indeed just a question of setting a flag, and it's done for you, you never need to know about, let alone consider encryption of, session cookies, so this is outsourced down the stack (and sufficiently clean for anything I can think of). Just not as far down as the HTTP standard suggests is possible.