We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As of now, we only handle one, which is terribly error-prone, we'll want to get an array of connectors.
The text was updated successfully, but these errors were encountered:
e52d0f1
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.
Sorry, something went wrong.
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.
/proxy/arc
No branches or pull requests
As of now, we only handle one, which is terribly error-prone, we'll want to get an array of connectors.
The text was updated successfully, but these errors were encountered: