I would like to be a real-time collaborative editor (like Google Docs). I have been successful in implementing it.
So now I am able to send text between two clients. But I have to understand how to manage a collaborative document / editor.
I have read about the operational change, so what do you think about the following setup:
There are three clients: Client A, Client B, Client C
< P> All changes connected through all the three websites are sent to the API (this will be a full Jason object). Customers receive Jason object and accordingly they have nothing left to the database on / insert / delete / update content. My easiest way would be, only Client A (he's impressive) saves the database on every change (including changes to other customers). With this solution I will not have to apply the OT at the API level. If the client leaves A, another client will become effective and save the database.My only issue is right now, there is no easy solution to handle OT among the customers. / P>
Do you have any suggestions? Does this solution understand or is it completely nonsense?
My TechStack is up to now:
Backbone / jQuery
MySQL
Java Servlet / Talket 7 (JT is better with WS - It will be implemented later)
Good if it fits with this stack;)
Best Fabian
OK - so I'm solving it myself a great project called WebState if you want to make rich-text-editing in real-time, Should check.
Best Fabian
No comments:
Post a Comment