Route caching built in
The ability to define default route caching would be a useful feature for performance reasons.
Any thoughts on furthering this into 1.0 or 1.1?
As long as this is solvable in userland, it does not have a high priority.
@shopblocks When you test and make the following ready for the framework's 1.1 branch, i'll merge it: https://github.com/UnionOfRAD/framework/commit/11d8d7a1b080b13f37e213caffac7fe4acc75305
Tested the code above on a project. The project had many routes with the same $template but different params, so the cache $key didn't work for me. So I did some adjustment and made it work but I did not get any performance gain (in fact, caching made it worse for me). But then again, I could be doing it wrong.