title: Castle Windsor Interceptor to solve caching aspect
body: <p>I recently decided to implement caching using the interceptor functionality from castle.  It works fine.</p>
  
  <p>My question:  If I wanted to avoid the interceptor for a particular call, what strategy would you suggest using?</p>
  
  <p>I've already determined I could have two implementations of a given service one that supports the caching aspect and one that doesn't.  I could then call the appropriate one from wherever.  I don't like that for many reasons.</p>
  
  <p>I'd be ok with invalidating the cache at the point I knew it would be invalid, but I couldn't come up with a good solution following this line of thinking that still kept caching concerns out of my code.</p>