This is cool! I've been working on something similar in Go, but I haven't spent ...

c0da · on Dec 30, 2016

Thanks! My implementation is currently front-end only.

Here's the code that simulates all the client/server communication: https://github.com/cricklet/blue-ot.js/blob/master/js/ot/orc...

It shouldn't be too hard to take that and put it in an actual client/server architecture. The client needs to have a way to send local operations to the server (this can just be an endpoint on the server) and the server needs a way to broadcast operations to all clients (probably webRTC?).

grizzles · on Dec 30, 2016

Hey Kenrick, I agree - WebRTC would be a good choice since it allows out of order packets, that can speed stuff up quite a bit.

Did you see this article? It was posted on HN yesterday. It links to a gh project that might be useful for your project. https://getkey.eu/blog/5862b0cf/webrtc:-the-future-of-web-ga...

akanet · on Dec 31, 2016

I'm going to try to implement this in my app. I use Firebase/Firepad for true p2p OT but it's become cumbersome. Do you have additional thoughts about communication channel implementation?

mandeepj · on Dec 30, 2016

> all clients or to all interested clients.

> (probably webRTC?). It can also be done with SignalR.