-
Notifications
You must be signed in to change notification settings - Fork 534
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
custom connection type #567
Comments
Unfortunately there is currently no way of achieving this without modifying the library itself. If your broker supports MQTT v5 I'd suggest taking a look at the v5 client because it's design does allow this kind of thing. |
my broker doesn't supports MQTTv5. |
It's not something I plan to add (you are the first person I've heard from who has a need for this). If you feel that you can add this in a way that does not impact other functionality or add too much complexity then please feel free to submit a pull request. |
hi, i hava added this feature and submit a PR. |
Hello, we are interested in such a feature as well, as we look to use OpenSSL TLS library instead of golang default one. @carr123 is it possible to contribute to that PR? |
Hi @MattBrittan thanks for sharing and referring to the need. I looked at PR #569 and is seems fine to our use case. I assume that we can convert tls.config params to openssl context parameters (well, tls is tls). however have a concern that there will be a need other parameters for future transport types. // connectionArgs is an array of future transport parameters or maybe do it the ClientOptions way: |
Thanks @GilAddaCyberark - unfortunately that doesn't work because there is no mechanism to pass the |
@GilAddaCyberark hi, i(carr123) encounter some problem to summit a PR. |
I have accepted PR #574 which I believe should resolve this request. |
@MattBrittan very good ! thanks. |
hi, i want to add my own connection type, currently i need to modify your code at
github.com\eclipse\paho.mqtt.golang\netconn.go
inopenConnection
function, add a new case branch.is there a better way to do that, without modifying your code ?
thanks.
The text was updated successfully, but these errors were encountered: