Task #7128 (closed)
Opened 13 years ago
Closed 12 years ago
Evaluate 1.3 caching infrastructure
| Reported by: | cxallan | Owned by: | atarkowska |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | Web | Version: | n.a. |
| Keywords: | n.a. | Cc: | python-team@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
As of Django 1.3 a new caching infrastructure is now in place that is much more functional and supports a series of more advanced and capable backends. It should be evaluated potentially as a replacement for the rather broken WebGateway (#6752) caching. An overview of the new caching infrastructure can be found here:
Change History (1)
comment:1 Changed 12 years ago by cxallan
- Resolution set to invalid
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
We've decided not to make any use of the Django 1.3 caching infrastructure in milestone:OMERO-Beta4.4. Closing, we can re-open or annotate anything we find out about the caching infrastructure in the future here as needed.