Move connect and disconnect to gateway topic and set retain=1 about gateway-connector-bridge HOT 4 CLOSED

Having a pub/sub broker to track connection state feels a bit hacky but it is going to work.

If it really is the connection state, why not using a message with a boolean field whether the gateway is active/available?

from gateway-connector-bridge.

In my opinion the pub/sub broker already keeps track of the connection state, so this proposal only adds a way to inform the bridge of this state (and of the auth information). The bridge also needs the auth information from the gateway (which is stored in the connect message) in order to start the connection with the backend.

The proposed solution is the most elegant solution I could think of. Let me know if you have a better solution that (a) informs the bridge of the connection state and (b) informs the bridge of the information needed for auth and (c) survives restarts.

from gateway-connector-bridge.

Ideally, the less hacky approach imo, is that (a) and (b) are handled by the authentication plugin on connect/disconnect, and (c) on reconnect, and it reports this not through the pub/sub messaging but through another endpoint. It depends on the concerning broker whether an authentication plugin is capable of this and here lies the constraint. So it is going to work, and it is portable across brokers, so let's do it.

from gateway-connector-bridge.

iceboxing this for now

from gateway-connector-bridge.