You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Introduce a Ctl method for Chan. Different channel types (e.g., MQTT, HTTPServer) can then support different Ctl requests. For example, the MQTT channel type should support subscribeandunsubscribe.
Currently, for several channel types, the method Sub will return a "not implemented" error. In other words, Sub doesn't make sense for many channel types. Also the corresponding Unsub (for "unsubscribe"), which does make sense for an MQTT client is not actually available today. In this proposal, the MQTT channel would support a "subscribe" Ctl request and an "unsubscribe" Ctl request. Possible example of the former:
- ctl:
subscribe:
topic: 'foo/+'qos 1
(Might want an explicit payload?)
How would a test get the results of that call? Perhaps via the usual Recv mechanism on a designed topic (e.g., ctl)?
- recv:
topic: ctlpattern:
success: true
?
The text was updated successfully, but these errors were encountered:
A suggestion from @robertfarnum:
Introduce a
Ctl
method forChan
. Different channel types (e.g.,MQTT
,HTTPServer
) can then support differentCtl
requests. For example, theMQTT
channel type should supportsubscribe
andunsubscribe
.Currently, for several channel types, the method
Sub
will return a "not implemented" error. In other words,Sub
doesn't make sense for many channel types. Also the correspondingUnsub
(for "unsubscribe"), which does make sense for an MQTT client is not actually available today. In this proposal, theMQTT
channel would support a "subscribe"Ctl
request and an "unsubscribe"Ctl
request. Possible example of the former:(Might want an explicit
payload
?)How would a test get the results of that call? Perhaps via the usual
Recv
mechanism on a designed topic (e.g.,ctl
)??
The text was updated successfully, but these errors were encountered: