Skip to content

Conversation

@michaelneale
Copy link

I modified client_connection.rb to look at the result returned from the connect_error_callback - if true is returned - it will then start the connection process again - calling the connection block again. This means that a different backend (remote) can be given - and the client is none the wiser (not unlike what haproxy does).

There is also a load_balancer.rb which shows this in action. I also threw in that some randomiser-based weighted load balancing (something I am doing) - I tried randomising as it means that I don't have to have any shared state regardless of how many proxymachines I have running (of course I could count connections - but some other changes needed).

There may also be pictures of my dog, can't remember what else I included.

Would love any thoughts/feedback (I have a few alternative approaches I would like to try).

@lstoll
Copy link

lstoll commented Dec 18, 2015

@michaelneale would you mind rebasing against master?

@michaelneale
Copy link
Author

@lstoll I will get right on that.

types into invisible typewriter

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.

2 participants