Sean Farrow

With v7 of the Microsoft.Extensions.Caching.Abstractions NuGet package we can support all the current frameworks. The only thing that looks hard to do with the current IDistributedCache implementations is return the...

Possibly, but firstly, what is the purpose of storing the keys in a separate dictionary in the in-memory implementation? Once I understand that, I may be able to come up...

Yes, massively, thanks. My feeling is we probably could get away with a single dictionary, but I wonder whether we wait and see what .Net 8 is going to give...

That makes sense. I think we should provide an implementation for Redis out of the box. Microsoft also provide a distributed cache implementation that supports SQL server, but I don't...

I completely agree. I’ll start work on that over the next few days. Thanks, Sean. From: Kevin Dockx ***@***.***> Sent: 07 February 2023 18:58 To: KevinDockx/HttpCacheHeaders ***@***.***> Cc: Sean Farrow...

I'm currently implementing this and wondered whether you had any objection to changing the FindStoreKeysByKeyPartAsync method of the IValidatorValueStore to return an IAsyncEnumerable. This won't help the in-memory implementation but...

I’m thinking about changing the contract. The distributed cache will just be another implementation of the IValidatorValueStore interface, but due to the way we have to query Redis, it makes...

I'll finish this next weekend now that issue #114 has been merged.

I'm very close to finishing this, but the remaining issue we have left is how to re-create keys. Currently there is no way of knowing which part of the key...

I think my main question was what types/assemblies do we want added by default? From: Jeff Ward ***@***.***> Sent: 10 November 2022 16:26 To: Testura/Testura.Code ***@***.***> Cc: Sean Farrow ***@***.***>;...