tree b32a1c8159193cfebde1037b8e0f484e84d1caa6
parent 38dcddad1a32935f842aca39dd1278c5b7806ed9
author Chris Sosa <sosa@chromium.org> 1355175551 -0800
committer Gerrit <chrome-bot@google.com> 1355223731 -0800

Don't do any caching logic if we are only serving payloads.

Currently, if we are only supposed to be serving images, the devserver
-at startup- might still try to clean its cache. This is unintended and
incorrect. If we are only supposed to be serving payloads, we shouldn't
have any additional side-effects.

BUG=chromium-os:34768
TEST=Ran w/ w/out archive_dir also ran unittests + pylint + --clear_cache w |
w/out data. A canary with vmtests and a paladin.

Change-Id: I7f97f9748f7eecac9da443b5881adac443f00fcd
Reviewed-on: https://gerrit.chromium.org/gerrit/39510
Commit-Ready: Chris Sosa <sosa@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>