Improve cache specificity #22

New Issue

timw4mail · 2019-02-07T08:36:59-05:00

timw4mail commented

2019-02-07 08:36:59 -05:00

Right now the cache setup is pretty crude - any API update invalidates the entire cache, and only the currently viewed list section is added to the cache when the cache is empty.

Instead, the cache should be more granular - each list item should be able to be independently updated.

Have a different cache pool for pages (media, characters, people) than for the lists
Update the cache setup so that each list item can be independently updated

Right now the cache setup is pretty crude - any API update invalidates the entire cache, and only the currently viewed list section is added to the cache when the cache is empty. Instead, the cache should be more granular - each list item should be able to be independently updated. * Have a different cache pool for pages (media, characters, people) than for the lists * Update the cache setup so that each list item can be independently updated

timw4mail self-assigned this 2019-02-07 08:36:59 -05:00

timw4mail added the

Planned Feature

label 2019-02-07 08:36:59 -05:00

timw4mail added this to the v5.1 milestone 2020-07-28 17:47:52 -04:00

timw4mail removed this from the v5.1 milestone 2020-08-04 10:07:04 -04:00

timw4mail referenced this issue from a commit

2024-01-23 13:24:34 -05:00

Merge branch 'master' into 'develop'

timw4mail referenced this issue from a commit

2024-01-23 13:44:42 -05:00

Merge branch 'master' into 'develop'