You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a channel is not correctly updating it's operational status or is faulting frequently, we could end up with some stack overflow issues. It might be beneficial to have a way of supplying a retry policy to the sending stream to shut down inoperative channels.
The text was updated successfully, but these errors were encountered:
I think it's one of those things that everyone will have a unique requirement and want specific behavior, so providing a stock implementation is dead in the water. There are 2 ways I can think off immediately that can make most people happy:
Let people bring their own sender to the table. By registering MyRetrySender<T> and having the implementation take a collection of ISendingChannel<T> you can make your own sender however you wish (this is a no code solution)
Have an IRetryPolicy or similar with a method bool Retry<T>(T message, Exception ex, int retryCount) and let the consumer provide an implementation.
If a channel is not correctly updating it's operational status or is faulting frequently, we could end up with some stack overflow issues. It might be beneficial to have a way of supplying a retry policy to the sending stream to shut down inoperative channels.
The text was updated successfully, but these errors were encountered: