Caching and headers

[eluser]Aquillyne[/eluser]
[quote author="beemr" date="1216773854"]Why not just extend the libraries you want to see changed, publish to the Wiki, and see if enough of the community is interested to elevate the extensions to EllisLabs? If you want me to, I'll turn your wiki into a MY_Output extension. That way, the community can try it out risk-free, and EllisLabs will be able to see the buy-in before they make your core changes.[/quote]

I seeeeee.

This was my original gripe. It's a horrible MY_Output extension. The code I've given is a mix of original code and basically 10 lines of new or changed code. You'd have to extend the output class and override 2 core functions, each of which is about 70 lines long - so 140 lines - just to effectively change 10 lines. It's ugly.

I'm proposing this as a patch outright because I can't see how you, me, EllisLabs or anyone wouldn't benefit from it immediately. As I demonstrated earlier, it cannot possibly break any existing code, it only adds functionality in a place where it's so clearly missing that the CI code contains a comment bewailing it's absence. I'm proposing a core change rather than a class extension because it's not adding anything: it's fixing a problem with one of CI's core functions, caching.