Caching api review changes

[kichalla]

@Tratcher

Please note:

• The changes to Redis cache implementation is incomplete...wanted to get initial input on the MemoryCache changes.

[kichalla]

Should get from resources?

[Tratcher]

⌚ So far so good, but I only reviewed the memory cache components. Distributed Cache and Redis haven't completed API review yet, so you might as well leave them out of the PR until we get memory cache finished.

Let me know when you're ready to work on entry links.

[davidfowl]

Can you have an example of a set call that doesn't chain the options into a single argument?

var options  = new CacheEntryOptions()
                                .RegisterPostEvictionCallback((echoKey, value, reason, substate) => 
                                     Console.WriteLine(echoKey + ": '" + value + "' was evicted due to " + reason), state: null);

result = cache.Set(key, new object(), options);

But with better formatting

[kichalla]

Sure

[Tratcher]

Distributed cache will not use the same options type as memory cache, many of the options are different. Give it its own options type like before.

[kichalla]

Sure, this becomes DistributedCacheEntryOptions as per yesterday's review.

[kichalla]

Updated. /cc: @Tratcher

[Tratcher]

IEntryLink.SetAbsoluteExpiration probably needs a new name like AddAbsoluteExpiration that indicates it's not strictly an overwrite.

[Tratcher]

pending the redis test run.