Adapt to production MQTT protocol #1
Comments
@johanstokking, @htdvisser may I have your input on these changes for node-ttn to work with production? Changes in the message formats:
Changes in the broker address
Other improvements while we're at it: |
The URLs for the Load Balancers of our datacenters are currently as follows:
We might want to create additional CNAMES for mqtt/router/broker/handler, but maybe the plain URLs are more clear? |
Thanks @htdvisser, I'd suggest that the Client constructor will accept:
We just need to be sure that the we never introduce something like |
I think defaulting to |
Clear, thx! |
As part of the refactor I've simplified the API https://github.com/TheThingsNetwork/node-ttn/blob/refactor/src/example.js
For discussion on standardising on a simple API for SDKs: https://docs.google.com/document/d/1nk6_Tty1WZ3RCl0hOVspLq6h87ZrQQiL2OjFguNdK7s/edit?usp=sharing |
See https://github.com/TheThingsNetwork/ttn/tree/refactor/mqtt
The text was updated successfully, but these errors were encountered: