Static File caching

[jkniest]

I am currently thinking about implementing a second way of caching the final html results. The current implementation works fine but needs to boot the full application to serve the static files. Currently it "only" skips the whole controller / view logic.

Inspired by laravel.com maybe it would be better to save all cached results in a dedicated folder (something like "public/cached") which is called from the webserver (apache / nginx) directly.

This would be a massive breaking change and I don't think this would be the right approach for every one since the server configuration needs to be modified.

I will probably add both ways of caching into the application. So the developer can decide what mode they want to use. There would be a new configuration option in the config file.. something like: mode: 'default'. (default / static would be the two options here).

Also the whole documentation must be modified for this. I will probably try to avoid breaking changes. The old mode should be the default and it should work like now without changing anything.

ToDos:

• Implement logic to separate different modes
• Reimplement the default mode
• Implement the static mode (write to file, path configurable)
• Modify readme file to include the different modes and server configuration changes

---

I am still thinking if I should implement this or not.. maybe I will make a new package for this. Something like HTMLStaticCache.