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

Where would reconnect logic reside? #110

Open
jacobslusser opened this issue Jan 10, 2021 · 1 comment
Open

Where would reconnect logic reside? #110

jacobslusser opened this issue Jan 10, 2021 · 1 comment

Comments

@jacobslusser
Copy link

@davidfowl, suppose I was working on a Redis client and wanted to implement automatic reconnect if the TCP connection is lost. This would be seamless to the client caller.

Would you have a recommendation of where that reconnect logic would go in the Bedrock stack? Transport? Middleware? Protocol? or way up in the Client library? Ideally as little teardown and build up as possible would be the desire so my thinking is to put it as far down as possible. If you agree, just wondering how you might see the ConnectionContext and IConnectionFactory interacting in such a case.

Thanks for the work on this project and your many other contributions.

@davidfowl
Copy link
Owner

You can consider making a wrapping ConnectionContext that reconnects or you can do it on top with your own client API like SignalR.

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