-
-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
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 Synchronizer #158
Comments
ok! this sounds fun... |
@jamesgpearce I've been eager to learn about WebRTC for a while - I'd like to take a crack at this though I'll need to get up to speed |
Architecture question after reading about WebRTC: I am assuming there's no desire nor intent for a signalling server to be built in to Tinybase - therefore my focus is on providing a WebRTC layer and interface to a(ny) signaling server - similar to what's asked for here: yjs/y-webrtc#55. Is that correct? |
I think that would be the best. I don't want to carry heavy dependencies - assuming you can find a way to pass in the server you need as an argument. (That's the pattern I try to use everywhere else there are integrations with TinyBase) |
Is your feature request related to a problem? Please describe.
Currently to synchronize remote clients the only way is through websockets. This requires a WS server, which can be non trivial to maintain
Describe the solution you'd like
It would be great to have a synchronizer working with webRTC in order to enable peer to peer data update. A signaling server is still required, but it's lighter and data would be exchanged directly between clients
Describe alternatives you've considered
y-webrtc works just fine, it would be great to ingreate it in the project.
The text was updated successfully, but these errors were encountered: