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 handling of multiple sproxyd connectors #5

Closed
ghost opened this issue Nov 30, 2015 · 2 comments
Closed

Add handling of multiple sproxyd connectors #5

ghost opened this issue Nov 30, 2015 · 2 comments

Comments

@ghost
Copy link

ghost commented Nov 30, 2015

As of now, we only handle one, which is terribly error-prone, we'll want to get an array of connectors.

@ghost ghost added the enhancement label Nov 30, 2015
@ghost ghost mentioned this issue Nov 30, 2015
@ghost ghost closed this as completed in e52d0f1 Dec 2, 2015
@JordanP
Copy link

JordanP commented Dec 2, 2015

It's common to have one sproxyd connector on http://node1:81/proxy/bpchord and another on http://node2:81/proxy/chordbp. With this commit because the "path" is shared across all the connectors, it's not possible.

It's a detail though :) But it might be worth to consider it as an enhancement.

@ghost
Copy link
Author

ghost commented Dec 2, 2015

We specifically only use /proxy/arc at the moment with the lack of erasure coding on the network level, but yeah, this could be done easily.

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

No branches or pull requests

1 participant