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
Is this a feature relevant to companion itself, and not a module?
I believe this to be a feature for companion, not a module
Is there an existing issue for this?
I have searched the existing issues
Describe the feature
The satellite protocol is ASCII over TCP. This is good for simple backend implementations, and more easily allows for use on arduino or similar microcontrollers.
In some cases, it would be more useful to be able to do this over websockets. This would make it easier to allow for running in certain environments (eg kubernetes), and for applying custom authentication to the service.
It should be the exact same protocol talked across both, making it a drop in replacement of just the transport.
This should run on its own port, so that it can bind to all interfaces all the time.
Ideally, after this change is made the satellite client should be updated to support this websocket as an option
Usecases
No response
The text was updated successfully, but these errors were encountered:
Is this a feature relevant to companion itself, and not a module?
Is there an existing issue for this?
Describe the feature
The satellite protocol is ASCII over TCP. This is good for simple backend implementations, and more easily allows for use on arduino or similar microcontrollers.
In some cases, it would be more useful to be able to do this over websockets. This would make it easier to allow for running in certain environments (eg kubernetes), and for applying custom authentication to the service.
It should be the exact same protocol talked across both, making it a drop in replacement of just the transport.
This should run on its own port, so that it can bind to all interfaces all the time.
Ideally, after this change is made the satellite client should be updated to support this websocket as an option
Usecases
No response
The text was updated successfully, but these errors were encountered: