From: Richard M Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: ttn@gnuvola.org, bpt@tunes.org, emacs-devel@gnu.org
Subject: Re: GSoC: collaborative editing
Date: Mon, 13 Apr 2009 19:10:54 -0400 [thread overview]
Message-ID: <E1LtVIk-00053O-OC@fencepost.gnu.org> (raw)
In-Reply-To: <jwvvdp8wiv4.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 13 Apr 2009 13:44:20 -0400)
A peer-to-peer approach has advantages, of course, but it also makes it
very difficult to recover a total ordering and hence guarantee that
every client sees the same content.
Yes, but it should be possible to set it up so that conflicts are
reported. They will only happen when two people edit the same area
in a short period, and that is asking for trouble anyway.
It is very important to promote peer-to-peer methods of doing various
collaborative tasks, because servers cause issues of control vs
freedom, and peer-to-peer is the only way to avoid them.
next prev parent reply other threads:[~2009-04-13 23:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 20:07 GSoC: collaborative editing Brian Templeton
2009-04-12 18:02 ` Michael Albinus
2009-04-13 1:22 ` Miles Bader
2009-04-13 9:08 ` Michael Albinus
2009-04-13 14:43 ` Thien-Thi Nguyen
2009-04-13 16:11 ` Thomas Lord
2009-04-13 22:04 ` Brian Templeton
2009-04-13 22:49 ` Thomas Lord
2009-04-14 3:41 ` Brian Templeton
2009-04-14 5:24 ` Thomas Lord
2009-04-13 22:52 ` Thomas Lord
2009-04-14 10:42 ` Thien-Thi Nguyen
2009-04-15 2:03 ` Thomas Lord
2009-04-13 17:44 ` Stefan Monnier
2009-04-13 23:10 ` Richard M Stallman [this message]
2009-04-13 23:32 ` Brian Templeton
2009-04-14 3:01 ` Stephen J. Turnbull
2009-04-14 4:02 ` Brian Templeton
2009-04-14 7:29 ` Stephen J. Turnbull
2009-04-14 9:09 ` Brian Templeton
2009-04-15 2:02 ` Thomas Lord
2009-04-14 21:14 ` Richard M Stallman
2009-04-15 2:18 ` Thomas Lord
2009-04-15 1:19 ` Brian Templeton
2009-04-15 1:27 ` Brian Templeton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1LtVIk-00053O-OC@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=bpt@tunes.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=ttn@gnuvola.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.