Caching and headers

[eluser]Aquillyne[/eluser]
Okay I've been looking over the code and here's what I think.

I don't need to go as far as the Suffix extension. I just want to cache headers.

I'd need to extend the Output class. But, looking at the code, I'd have to extend a huge amount (which I'm never fond of, because it doesn't make you update-proof). On top of it, I'd be extending a huge amount of code just to access 10 or so lines in 2 functions.

So the Suffix extension is too much, and extending the Output class is too ugly. The solution?

The CI code for the Output class actually reads:

Code:

/**
* Set Header
*
* Lets you set a server header which will be outputted with the final display.
*
* Note:  If a file is cached, headers will not be sent.  We need to figure out
* how to permit header data to be saved with the cache data...
*
* @access    public
* @param    string
* @return    void
*/    
function set_header($header)
{
    $this->headers[] = $header;
}

Yes, even the developers admit this limitation. The solution: shout loud enough for the developers to hear!

The Suffix extension proved that it's not hard to cache headers. CI is also storing the time-stamp inside the file. Just store the headers there too. It takes 10 lines of code.

Please, someone get this to a developer's eye and beg them to work it into the next CI update. It will save me so much trouble, it would make CI better, and it would allow them to remove that embarassing comment... :cheese: