Added possibility to specify NotificationHandlingStrategy when sending notification

[lkovalyk]

By default I use sorted StopOnException strategy, but in some cases I have to handle notifications with ParallelWhenAll strategy to resolve performance problem.

[sizovs]

Hey @lkovalyk

Thanks for the PR. The current approach to multiple notification handling strategies is by setting up multiple instances of PipelinR – one per strategy. Currently, I am reluctant to merge the PR because:

1. Handling an infrequent use case at the Pipeline level would make Pipeline interface heavier for everyone.
2. When life allows, a single approach is better than multiple ones because it's easier to reason about and troubleshoot notification handling when it's configured in a single place.
3. When life allows, it's good not to couple Pipeline – the client interface – with strategies and other "details."

That said, for your specific use case, you can create a separate PipelinR instance and override the notification strategy on that instance.

Would that solve your problem?

[lkovalyk]

Hi @sizovs
Thx for the solution, and it solved my problem.