Move image caching into the store rather than a middleware
Registered by
Mark Washenberger
Currently glance image caching lives in a wsgi middleware. This design requires us to duplicate important business logic like notifications and serialization all for the sake of caching image data. A more natural place to accomplish this caching would be to put a cache on top of the store layer, so that a call to store.get_
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
<jbresnah>
As this work is designed I would like to consider the idea of automatically adding the cached location to the set of 'multiple-
</jbresnah>
markwash wishlist 2014-02-15
(?)