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

Use connection string instead of address + port. #67

Closed
fawadasaurus opened this issue Aug 2, 2022 · 1 comment
Closed

Use connection string instead of address + port. #67

fawadasaurus opened this issue Aug 2, 2022 · 1 comment

Comments

@fawadasaurus
Copy link
Contributor

Most protocols that are worthwhile today take url based endpoint and as a developer I just want to throw url in without having to figure out command line options - throwing url at something makes me not need make decisions how to pass things to separate CLI arguments - URLs often also carry other information in parameters.

You can always in the future add further CLI options for protocols that require different scheme but URL should be the default that covers the most.

Most MQs including nats have URL scheme: https://docs.nats.io/using-nats/developer/connecting

Even WebSockets are modelled as ws[s]:// and mqtt mqtt[s]:// as well etc ..

And yes URL as a tried and trusted standardised scheme supports multiple protocols, encryption / authentication options, connection options as well as other supplied often proprietary protocol / application specific arguments at ease

Originally posted by @pinkforest in #66 (comment)

EstebanBorai added a commit to EstebanBorai/wasmflow that referenced this issue Sep 8, 2022
Replaces current `address` and `port` options from the RPC
CLI on wafl with a single URL to use a connection string.

Fixes: candlecorp#67
@pkedy
Copy link
Contributor

pkedy commented Jan 9, 2023

Closing after nanobus switch

@pkedy pkedy closed this as completed Jan 9, 2023
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 a pull request may close this issue.

2 participants