PIAB: Why does CachingCallHandler use ASP.NET cache and not Caching Application Block?

Topics: Caching Application Block , Policy Injection Application Block
Sep 24, 2007 at 2:08 AM
I'm trying to understand why the CachingCallHandler attribute in the PIAB uses ASP.NET cache and not Caching Application Block? And why has no one else seemed to ask this question? Maybe I'm just missing something here...

Going along with the general theme of the Enterprise Library, I would have thought it would make more sense to tie PIAB in with the Caching App Block to provide a consistent and platform agnostic (i.e. not tied into System.Web) caching capabilities.

Wouldn't an alternative architecture be to either give the option to configure whether to use ASP.NET or Caching Application Block from PIAB, or alternatively wire PIAB to use the Caching Application Block and provide a new ASP.NET Backing Store for the Caching Application Block?