EasyCaching

EasyCaching copied to clipboard

1.6version Wroked with MediatR framework throw nullreferenceException

1

if you use MediatR and EasyCaching and also use two level cache . you will get nullreferenceException at MediatR handler layer. at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task) DependencyResolutionException An...

charzhao

GetByPrefix method on IHybridCache

5

I am in dare need of the GetByPrefix method on IHybridCache, how can I add it back. I learned it was removed from 0.5 version. Please help.

umar-ulabs

期望对接Freeredis

4

bebestmaple

Eviction hooks

4

Hi there, Does EasyCaching support any callback capabilities so we can be notified when an InMemory item is evicted/expires? I can't seem to find any documentation. thanks!

jasenf

Publish without basicproperties

2

BasicProperties is a fundamental mechanism to define behaviors of the message, like if the message is transient or durable. https://github.com/dotnetcore/EasyCaching/blob/bc4a0177cf2cc9c220afbee6aafc6065770af239/bus/EasyCaching.Bus.RabbitMQ/DefaultRabbitMQBus.cs#L94

luizcarlosfaria

This Async Implementation is fake

1

On source code https://github.com/dotnetcore/EasyCaching/blob/bc4a0177cf2cc9c220afbee6aafc6065770af239/bus/EasyCaching.Bus.RabbitMQ/DefaultRabbitMQBus.cs#L113 ExchangeDeclare is a blocking and painful operation, run entire publish as a task, sounds less fake .

luizcarlosfaria

Consumer is considering only EventingBasicConsumer ignoring AsyncEventingBasicConsumer

1

This consume implementation is considering only EventingBasicConsumer and ignoring async consumers, with AsyncEventingBasicConsumer. https://github.com/dotnetcore/EasyCaching/blob/bc4a0177cf2cc9c220afbee6aafc6065770af239/bus/EasyCaching.Bus.RabbitMQ/DefaultRabbitMQBus.cs#L158 it's affect this source too https://github.com/dotnetcore/EasyCaching/blob/bc4a0177cf2cc9c220afbee6aafc6065770af239/bus/EasyCaching.Bus.RabbitMQ/DefaultRabbitMQBus.cs#L58

luizcarlosfaria

Force every publish to execute ExchangeDeclare produce lacks of performance

1

When the code calls ExchangeDeclare, client send a command to server to ensure that exchange exists with these parameters. As a library do you don't know if the exchange must...

luizcarlosfaria

Opinative exchange type is a anti-pattern

1

Force type of exchange is a anti-pattern. The type of a exchange is the unique responsibility of developer, never a generic publish can be opinative around this. https://github.com/dotnetcore/EasyCaching/blob/bc4a0177cf2cc9c220afbee6aafc6065770af239/bus/EasyCaching.Bus.RabbitMQ/DefaultRabbitMQBus.cs#L93

luizcarlosfaria

ConnectionFactory has many options specific of runtime environment. Assuming the you must perform the construction of this classes take for yourself a lot responsability to cover many cases. Use dependency...

luizcarlosfaria