This seems like a nice library but it would be even better
if it did not rely on System.Web.Caching.
For example, when I write a Windows service or
Windows application I cannot use the web cache, but I
could implement my own caching component instead.
Maybe you could change it so that the caching method
can be replaced by something else? With a common
interface and a method for setting the caching
mechanism this should not be that hard to accomplish I
think. You could just wrap the existing cache and just
forwards the calls to it so you don't have to spend any
time to implement your own.
Logged In: YES
user_id=440341
Sorry, I just found out that the more recent version uses
Microsoft Caching Application Block. I will take a closer look
at it now.