emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Loury <konubinix@gmail.com>
To: "François Pinard" <pinard@iro.umontreal.ca>,
	"Torben Hoffmann" <torben.lehoff@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: colorg: Protocol [was: Re: Rudel - Real-Time collaborative editing of Org-Mode files]
Date: Mon, 14 Jan 2013 11:29:40 +0100	[thread overview]
Message-ID: <87obgs12i3.fsf@konixwork.incubateur.ens-lyon.fr> (raw)
In-Reply-To: <86obguou20.fsf_-_@iro.umontreal.ca>

[-- Attachment #1: Type: text/plain, Size: 2180 bytes --]


This sounds really promising. But instead of creating your own protocol,
have you thought about extending an already existing one? I see that you
have read negative comments about tools using the obby protocol, but
have you read about the protocol itself?

For instance, even if the gobby seems quite a dead (not commit since
2011-08-07T16:07:00Z+0200), the obby protocol sounds like it has been
well thought and should worth give a look. See for instance the
annotated obby session[1].

By recreating a new protocol, you might be facing the same issues in
synchronization that gooby faced at some time and spending useless
effort trying to fix it.

As far as I can see, the only thing that appears to be missing in the
obby protocol is the possibility to move entries without deleting and
reinserting. This makes sense since it is specific to outlined
documents. Why not adding this feature to the obby protocol?

If the obby protocol or any other RTCE protocol does not fit your needs
causing the creation of a new protocol, I think it would be a good idea
to write why on your wiki page.

By the way, I tried this week end gobby server 0.4 and rudel client
(last git version) and it did not manage to connect to the gobby server
while a gobby client 0.4 succeeded. So sad...

I can't wait to see RTCE of org document!


[1] http://gobby.0x539.de/trac/wiki/AnnotatedObbySession
François Pinard <pinard@iro.umontreal.ca> writes:

> François Pinard <pinard@iro.umontreal.ca> writes:
>> So, inventing a protocol is still an avenue which I naively seek, and
>> for which I dared giving some thought recently, trying to stay on the
>> side of simplicity.
> Here is a stab at a simple protocol, which I documented in:
>    https://github.com/pinard/ColOrg/wiki/Protocol
> I have the start of colorg.el, and now intend to write the skeleton of a
> server.  Before committing them, I'll stretch both enough so they speak
> to one another.  Then we will have a sandbox to play with. :-)
> François

GPG Key    : 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE  5C36 75D2 3CED 7439 106A

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2013-01-14 10:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-21 18:50 Rudel - Real-Time collaborative editing of Org-Mode files Ciaran Mulloy
2012-12-23 23:18 ` Bastien
2012-12-25 13:22   ` François Pinard
2012-12-25 20:02     ` François Pinard
2012-12-26 21:44       ` Eric Schulte
2012-12-27  2:18         ` François Pinard
2013-01-01 22:04           ` Torben Hoffmann
2013-01-12 14:47             ` François Pinard
2013-01-12 23:33               ` colorg: Protocol [was: Re: Rudel - Real-Time collaborative editing of Org-Mode files] François Pinard
2013-01-14 10:29                 ` Samuel Loury [this message]
2013-01-14 14:38                   ` François Pinard
2013-04-01 20:46                     ` Torben Hoffmann

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87obgs12i3.fsf@konixwork.incubateur.ens-lyon.fr \
    --to=konubinix@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=pinard@iro.umontreal.ca \
    --cc=torben.lehoff@gmail.com \


* 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 public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).