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
Currently we can only connect to unix domain sockets, but its also useful to connect to TCP sockets.
To distinguish between the two, we should support something URLs, something like tcp://{ip}:{port} and unix://{path}.
tcp://{ip}:{port}
unix://{path}
To maintain backwards compatibility, it should be enough to assume its a unix domain socket when the user did no supply an URL (e.g. {scheme}:{rest}).
{scheme}:{rest}
What do you think?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently we can only connect to unix domain sockets, but its also useful to connect to TCP sockets.
To distinguish between the two, we should support something URLs, something like
tcp://{ip}:{port}andunix://{path}.To maintain backwards compatibility, it should be enough to assume its a unix domain socket when the user did no supply an URL (e.g.
{scheme}:{rest}).What do you think?
The text was updated successfully, but these errors were encountered: