Currently the app uses caching only for a small range of information.
This should be extended over the collection views. Ideally a view result would be cached by user and search parameters. The program would then serve the cached result if that request is made again.
If the user changes have counts or anything regarding cards (cards are updated or card versions are added / edited / deleted) these caches should be invalidated.
Perhaps it would be better to only save un-filtered views, though. The simple pages will probably be accessed often, but I don't imagine that users will repeatedly search / filter for the exact same parameters.
Currently the app uses caching only for a small range of information.
This should be extended over the collection views. Ideally a view result would be cached by user and search parameters. The program would then serve the cached result if that request is made again.
If the user changes have counts or anything regarding cards (cards are updated or card versions are added / edited / deleted) these caches should be invalidated.
Perhaps it would be better to only save un-filtered views, though. The simple pages will probably be accessed often, but I don't imagine that users will repeatedly search / filter for the exact same parameters.