failSafeCache added

There is a brittle relationship between "appendToResponse()" and "performActionNamed()." The RR-loop puts a fresh stylesheet response in the "cache" but only if it is stale. There are times when it's on the edge and not stale at that moment in the RR loop but when the direct action fires (while Safari interprets the head tags) when the DA will not have the canned response in the cache. It is for these times that something must be done. Hence the failSafeCache.

Signed-off-by: Aaron Rosenzweig <aaron@chatnbike.com>
Improved the null check

I was checking for the primary cache being null in the wrong way. Now fixed.

Signed-off-by: Aaron Rosenzweig <aaron@chatnbike.com>
logger improvement

The logger could have had a null pointer exception. This has now been removed.

Signed-off-by: Aaron Rosenzweig <aaron@chatnbike.com>