A coworker of mine has created a centralized Logging utility that works throughout our SP projects. It does a good job of queuing up a large number of logs, deals with logging level, etc.
However, it utilizes HttpContext.Cache in order to do some caching. This causes it to break when I attempt to Log from a custom timer job that I've written.
Can anyone think of a good way to fix this so that it'll work in a Timer, without completely tearing apart the architecture and re-writing it? Are there any System.Web.Caching.Cache objects that exist, or can be created, from within the SharePoint timer?