Feature - caching public/private/noCache

[JindrichPilar]

I am procesing Response object after app is done with it and I run into small problem with caching.

Right now there is only noCache method implemented by directly adding headers.

I propose to add privateCache() and publicCache() and change it's inner works from directly adding headers to change a flag and add headers when they are being send.
Which will allow easily change and detect current caching strategy.

[Rican7]

I wouldn't mind taking a pull request if you wanted to show how you might implement this feature.
Otherwise, implementing it in your own project is easily done without having to fork the code. All you'd have to do is extend the Response class and inject it in the dispatch() method.

[JindrichPilar]

I could implement it in my own project, but I think it deserves to be on original Response.
Implementation proposal #129

[chriso]

The problem with stepping into a full-featured Cache-Control helper is that there's a lot of other directives that you need to support. Some directives also expect an argument (e.g. max-age).

[JindrichPilar]

Initially I didn't inteded full-featured Cache-Control. But tried to implement it in #129