Reduced IMediator interface

public interface IMediator
{
    Task<TResponse> SendAsync<TResponse>(IRequest<TResponse> request, CancellationToken cancellationToken = default(CancellationToken));

    Task SendAsync(IRequest request, CancellationToken cancellationToken = default(CancellationToken));

    Task PublishAsync(INotification notification, CancellationToken cancellationToken = default(CancellationToken));
}

I’d keep all the existing handler interfaces, and inside the Mediator class decide which one is the right one to instantiate through cascading checks and then a cache to the right request.

[jbogard]

@remcoros yes. Supporting both models is annoying to say the least, and since calling frameworks are generally async-friendly (MVC back many versions, WPF w/ any modern MVVM frameworks, Xamarin too, messaging frameworks of NSB and MassTransit), it’s likely users calling code can be easily async.

But I’ve only confirmed this with our apps that use MediatR, where are you calling into it?

[jbogard]

Well it’s merged now anyway.