rogerkratz / mbcache Goto Github PK

throws InvalidOperationException 
Late bound operations cannot be performed on types or methods for which 
ContainsGenericParameters is true.

This doesn't invalidate cache (only false does)
factory.Invalidate(obj, method => obj.CachedMethod(), true);

CacheKey should build on parameter _type_ and not by its name.

Currently there is a problem with caching these two kinds of methods...

interface IFoo
  int Run(int a, int b);
  int Run(string a, string b);

...Run("1", "2") will share cache with Run(1,2).

When caching methods with multiple arguments, multiple cache items will be 
created.

As a complement to have one IMbCacheKey implementation for all entries, 
allow different ones per cached method.

Instead of manually run them twice, fix it automatically.

When a cached method returns null, mbcache thinks that this entry does not 
exist.

Add possibility to turn off/on caching of a component in runtime.

MbCache should log a warning if cache key of a parameter is the same as its 
type. This normally indicates that user hasn't defined how this type should be 
turned into a cachekey.

Using null as a parameter to a cached method causes crash

Better out of the box support for caching this...

void CachedMethod(IEnumerable<Something> foo)

...based on the content of foo.

If caching say Foo.Bar(int) today, overloaded Foo.Bar(string) will also be 
cached.

Fix either by...
* Allow user to choose to build proxies from interfaces or classes
* Build proxies from the interface instead

Make AspNetCache impl thread safe or, as an alternative, offer different impl 
based on whether thread safe is impl is needed or not.

make sure methods like

class T
  T Doit(T a, int b)

and

class Foo
  int DoIt<T1, T2>(T1 a, T1 b)

will be cached correctly based on parameter values AND types.

Remove strong dependency to Castle DynamicProxy. Also, add possibility to use 
other proxy fw

[deleted issue]

For performance reasons, make it possible to turn off statistics (micro 
optimization though).

Now ArgumentException is thrown if IFoo is an mbcache unregistered type when...

factory.Create<IFoo>();

* Correct exception should be rethrown
* Correct stack trace should be preserved

Both 
* when user invalidates something "bigger", like a complete type
* when cache entry expires

Having lots of cache entries result in huge memory usage because lots of long 
cache key strings.
It should be easier to create shorter ones.

Make MbCacheFactory serializable, eg to be able to cache it to disc.

If an ISomething is configured on MbCache, make it possible to make such an 
instance cacheable even if it's been created outside MbCache