Details
Description
TypeInfo and LockEngine all deals with some cache, this issue will eperate cache handling which are both handled by TypeInfo and LockEngine
TypeInfo and LockEngine all deals with some cache, this issue will eperate cache handling which are both handled by TypeInfo and LockEngine
After quite some refactoring around LockEngine, TypeInfo and ObjectLock it turns out that seperation of cache and lock handling at TypeInfo is not possible. I therefore resolve this as won't fix,