Yes. Maybe a CacheModel, following the likes of the request model?

Christophe Gijbels <notifications@github.com> wrote:
>> @@ -31,13 +31,22 @@ public override object GetData(ITabContext
>context)
>>                  // if more properties want to be displayed in the
>future, here's a list of properties available
>>                  //     Value - UtcCreated - State - UtcExpires -
>SlidingExpiration - ExpiresBucket - ExpiresEntryRef 
>>                  //     UsageBucket - UsageEntryRef -
>UtcLastUsageUpdate - Dependency - Key - IsOutputCache - IsPublic
>> -                items.Add(new { 
>> -                    Key = key,
>> -                    Value =
>Serialization.GetValueSafe(cacheEnumerator.Value),
>> -                    Created = GetCacheItemProperty(key,
>"UtcCreated"),
>> -                    Expiry = GetCacheItemProperty(key,
>"UtcExpires"),
>> -                    SlidingExpiration = GetCacheItemProperty(key,
>"SlidingExpiration")
>> -                });
>> +                try
>
>you would combine the cache entry retrieval with the property values
>retrieval in the `TryGetCacheEntry` method? And instead of returning
>`object` you want to return a custom `CacheEntry` instance with typed
>properties?
>
>I don't think there is an objection to do that, since de properties
>being asked for today aren't dynamic either, so adding properties in
>the future would mean a recompile anyway
>
>maybe @avanderhoorn has a reason why not to do that?
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/Glimpse/Glimpse/pull/652/files#r7926256