Yeah that’s a good point ideally the default behavior should be transparent so I’ve changed the default Cache-Control for ToOptimizedResults to max-age=0 so clients should revalidate each time unless error, adds a round-trip but still saves on serialization + bandwidth. (Change is now available on MyGet).
Yeah if you can create a blog post we’ll be able to reference/include it from the wiki where we’ll document the new built-in HttpCachingFeature.