-
Notifications
You must be signed in to change notification settings - Fork 2
TopicController response caching #89
Copy link
Copy link
Closed
Labels
Area: WebRelates to the `AspNetCore` or other web-related functionality.Relates to the `AspNetCore` or other web-related functionality.Priority: 1Status 5: CompleteTask is considered complete, and ready for deployment.Task is considered complete, and ready for deployment.Type: FeatureIntroduces a major area of functionality.Introduces a major area of functionality.
Milestone
Metadata
Metadata
Assignees
Labels
Area: WebRelates to the `AspNetCore` or other web-related functionality.Relates to the `AspNetCore` or other web-related functionality.Priority: 1Status 5: CompleteTask is considered complete, and ready for deployment.Task is considered complete, and ready for deployment.Type: FeatureIntroduces a major area of functionality.Introduces a major area of functionality.
Update
TopicControllerto conditionally set content headers that will be recognized by e.g.ResponseCachingmiddleware. This way, we can dynamically configure particular pages to participate in response caching based on a topic attribute (e.g.,IsCached).To accommodate this, we'll need to determine whether this will operate off of a fixed profile, centralized configuration values, or per-page values.
The best bet might be to rely on cache profiles, but to allow those to be selected via a
MetadataListattribute. This would permit settings to be configured per site and to vary per page, while still allowing those settings to be centralized.