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
There's something weird about the way that I'm handling the subscriptions.
For example, on the adapter messaging side, there should be an easy way to do multiple subscriptions. This is handled in the configuration file.
I'm not sure if it makes sense to have multiple subscriptions or not on the bot side (vexbot.messaging). Since the XPub/XSub are binding, I believe the answer is no.
I'd probably like to switch the defaults around, so that the subscription socket that the adapters are connecting to is tcp://my.address.here:4000 instead of the current tcp://my.address.here:4001
The text was updated successfully, but these errors were encountered:
There's something weird about the way that I'm handling the subscriptions.
For example, on the adapter messaging side, there should be an easy way to do multiple subscriptions. This is handled in the configuration file.
I'm not sure if it makes sense to have multiple subscriptions or not on the bot side (
vexbot.messaging
). Since the XPub/XSub are binding, I believe the answer is no.I'd probably like to switch the defaults around, so that the subscription socket that the adapters are connecting to is
tcp://my.address.here:4000
instead of the currenttcp://my.address.here:4001
The text was updated successfully, but these errors were encountered: