| Re: [mosquitto-dev] Bridge connection over Websockets |
Abilio Marques <abiliojr@xxxxxxxxx> writes: > I was wondering if it's there would be a downside of developing what you > need as an external program that sits between your two brokers, and does > the conversion to websockets. > > 1. Program is listening to TCP (+TLS) on one side. > 2. When a client connects, it starts the connection to the WS side. > 3. If connection on WS succeeds, it starts passing MQTT packets back and > forth between both sides. > > For authentication with username/password, you should have no problem (It's > passed transparently). For mutual authentication, maybe client credentials > need to be deposited in the program, so they are used on behalf of the > client. > > As a separate tool, it can evolve separate from mosquitto, without it's > development pace being limited by mosquitto's project. Also, it can be > developed in whatever language you prefer. At the same time, it would avoid > mosquitto's bridge code from becoming too complex for a not so popular > feature (I might be wrong). > > What do you think of the option of keeping it separate? I'm not the one wanting this, but since mosquitto already has server-side websocket support, adding in calls to use outgoing websockets would seem not that hard. As far as I can tell it will just take someone to write code, including an option to choose that and docs, and that seems vastly easier than writing an external translator. If there's some reason there is significant difficulty, that's another story, but nobody has explained why there would be.
Attachment:
signature.asc
Description: PGP signature