We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebRTC peering can be mixed into Ably remotes, but cannot be used stand-alone because it does not implement broadcast and requires signalling.
There is no reason that signalling and broadcast cannot alternatively be provided by the MQTT and Socket.io remotes options.
While this would be low cost to implement, it should be driven by field experience.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
WebRTC peering can be mixed into Ably remotes, but cannot be used stand-alone because it does not implement broadcast and requires signalling.
There is no reason that signalling and broadcast cannot alternatively be provided by the MQTT and Socket.io remotes options.
While this would be low cost to implement, it should be driven by field experience.
The text was updated successfully, but these errors were encountered: