~arsenal-devel/arsenal/0.x

Viewing all changes in revision 1095.

  • Committer: Bryce Harrington
  • Date: 2012-07-17 23:23:45 UTC
  • Revision ID: bryce@canonical.com-20120717232345-ld9hz0s0tc518wmg
Set up an explicit cache rather than reusing post-processed results.

This caches data before the exclude filters are run, rather than after.

This provides two benefits.  First, it helps us avoid re-pulling down
data that is going to get filtered by the exclude criteria.  Second, it
potentially lets us share the cache between multiple search configs that
have identical criteria for the search_tasks() call.

expand all expand all

Show diffs side-by-side

added added

removed removed

Lines of Context: