> These don't solve the major problems. If I want caching I can trivially implement it myself. It's a useless thing to implement at the architecture level. Leg

> These don't solve the major problems. If I want caching I can trivially implement it myself. It's a useless thing to implement at the architecture level. Legions of computer scientists and computer engineers disagree with you. Caching is fundamentally an architectural concern. >I'm frankly bored of talking to someone who knows nothing about protocol design.... Please point to your widely commercially deployed protocols before accusing others of ignorance. > ..but defends HTTP as a "proven" technology. It clearly isn't, it fails on many levels, and the whole web stack is completely fucked. Good day. You've demonstrated an astounding lack of respect for pretty much everyone on this topic here, and I'm finding it incredulous myself to have to tolerate the amount of bitterness being emanated from you. Why are you participating here it all, unless you just want to tell us we're all clueless, and you can feel superior?