Merge pull request #23 from fretje/parallel

Update readme with usage of `UseTaskWhenAll`

Author: KuraiAndras

CHANGELOG.md

@@ -1,3 +1,7 @@
+# 7.0.1
+- Remove unnecessary check for _options.UseTaskWhenAll
+- README: Add 'Parallel notification handling' section
+
 # 7.0.0
 - Removed Nuke
 - Updated to .NET 8

MediatR.Courier/MediatRCourier.cs

@@ -72,7 +72,7 @@ async Task HandleLocal(INotification n, CancellationToken c)
                 }
             }
 
-            if (_options.UseTaskWhenAll && tasks.Count > 0)
+            if (tasks.Count > 0)
             {
                 await Task.WhenAll(tasks).ConfigureAwait(_options.CaptureThreadContext);
             }

README.md

@@ -165,6 +165,26 @@ courier.SubscribeWeak<MyNotification>((notification, cancellation) => /*...*/);
 
 You can configure how the Courier awaits the sent notifications. To change the behavior modify the `CaptureThreadContext` property on the `CourierOptions` class. When using dependency injection, you can change this behavior during runtime, because the `CourierOptions` is accessible through DI.
 
+### Parallel notification handling
+
+You can configure whether notification handlers should run sequentially or in parallel by using the `UseTaskWhenAll` property on the `CourierOptions` class:
+
+```c#
+// Configure at registration time
+services.AddCourier(typeof(MyType).Assembly, options => 
+{
+    options.UseTaskWhenAll = true; // Enable parallel execution of handlers
+});
+
+// Or modify at runtime through dependency injection
+var options = serviceProvider.GetRequiredService<CourierOptions>();
+options.UseTaskWhenAll = true;
+```
+
+When `UseTaskWhenAll` is set to `true`, asynchronous notification handlers are collected and awaited concurrently using `Task.WhenAll`.
+
+When set to `false` (the default), handlers are awaited sequentially.
+
 ## Gotchas
 
 * No ordering is guaranteed when calling the subscribed methods