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

Add 'use_previous_backends' option. #106

Closed
wants to merge 1 commit into from
Closed

Add 'use_previous_backends' option. #106

wants to merge 1 commit into from

Conversation

jnb
Copy link
Collaborator

@jnb jnb commented Dec 11, 2014

  • This option defaults to true: if there are no default servers and a watcher
    reports no backends, then use the previous backends that we already know
    about.
  • Factor out code that updates @backends into the watcher base class.

This code is running in production with no issues.

* This option defaults to true:  if there are no default servers and a watcher
  reports no backends, then use the previous backends that we already know
  about.
* Factor out code that updates '@backends' into the watcher base class.
@igor47
Copy link
Collaborator

igor47 commented Jan 20, 2015

this is great; i've been wanting to do a refactor like this for awhile.

@jnb we talked about you becoming a maintainer of this repo. are you still interested? i have a few days this week to focus squarely on synapse, so i'm going to work on clearing out the current backlog and adding more unit testing. i've already done this for airbnb/nerve last week.

@jolynch
Copy link
Collaborator

jolynch commented Mar 12, 2015

Note, if you accept #115, that supersedes this change.

@igor47
Copy link
Collaborator

igor47 commented Apr 28, 2015

cool, we'll just work with #115

@igor47 igor47 closed this Apr 28, 2015
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

Successfully merging this pull request may close these issues.

3 participants