On Thu, 20 Jun 2013 06:59:18 +1200 David McNab <[email protected]> wrote:
> What I would ask is does your JS Leo allow concurrency? What a Cloud Leo > desperately needs is the ability to have n people editing it concurrently > and seeing where each other are at, just like with Google Docs. Currently the server isn't "pushing" stuff to the browser, but I expect it will be at some point. So simplistically you could have concurrency, but I've no idea how it would work out conflict wise. What happens when you're editing a node somewhere on a subtree and someone deletes the whole subtree? Or if people move subtrees around in inconsistent ways? I guess some level of etiquette might help, but to make it robust, I'm not sure. So my feeling was there are some hard parts out there, but starting simple will create a place to experiment. It's already almost at a point where it could be used for shared list making, with surprisingly little code. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
