One minor point: would it be a better idea not to convert the DateTime values that are passed to the Microsoft.Practices.EnterpriseLibrary.Caching.Expirations.AbsoluteTime constructor? It seems strange to me that it should interpret an incoming DateTime as
a local time value and then convert it to UTC. I think it should either accept a Local time and keep it as local time or accept a UTC time and keep it as UTC time. Otherwise it's kind of unexpected, especially since none of the methods have the words
"UTC" in them. Or at least, I was surprised by it....
This is with the January 2006 release.