Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retries #8

Open
herecydev opened this issue Jun 8, 2016 · 2 comments
Open

Retries #8

herecydev opened this issue Jun 8, 2016 · 2 comments

Comments

@herecydev
Copy link
Owner

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.

@smudge202
Copy link

I think this should be a focus on extensibility over functionality. Get Polly working with the library without it being hacky, job done?

@herecydev
Copy link
Owner Author

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:

  1. 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)
  2. Have an IRetryPolicy or similar with a method bool Retry<T>(T message, Exception ex, int retryCount) and let the consumer provide an implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants