This is a list of things considered for inclusion in the roadmap of Cache Control I found on my desktop. Some of them might already be implemented, and some of them might be discarded already for one reason or another. Create feature request issues of all bullet points if needed.

1. Improve page loading times
- Start loading (via AJAX) required replacement components as soon as header is loaded, since at this stage we already know which ones we need. This allows the browser to load the components and the main page simultaneously.
- Replace the loaded elements as soon as possible; either at the end of the ajax call if the page has already loaded(PAGEHASLOADED == true), or on document.ready, if the AJAX call has finished (AJAXCALLFINISHED == true).

2. Make Varnish grace setting follow headers set by CC
- This requires changes to the Varnish configuration, and possibly minor changes to the headers CC sends.
- The idea is to have pages cached by Varnish in grace mode to expire according to the expiry time set in CC configuration.

3. Add visibility classes
- Create optional page components that are loaded and shown per user or per role.
- For example classes CCShowToUser123 or CCShowToRoleauthenticated_user
- There was a plan to allow loading of these components securely. I forget the details, but it had to do with loading the component from a URL that includes a hash based on the user role(s), making it impossible to guess the URL.

4. Add a "fresh" button
- Add a button in the UI for users with the appropriate permissions
- This button would reload the page past Varnish, and might also create a cache purge request for the same URL
- The VCL might already have support for the required ?fresh GET parameter