[Standards-JIG] proto-xep: Shared XML Document Editing - related implementation
jean-louis.seguineau at laposte.net
Sat Oct 14 12:37:06 UTC 2006
You did mention this before ;)
The issue with the Netbean link lies in the lack of external documentation
beyond the Javadocs. The implementation is certainly interesting, but one
has to get into the code to have the detail. In particular, the Netbean
approach implements a message abstraction layer on top of the transport
layer. The only provided transport implementation is XMPP, but it is not
obvious to dig out the protocol used. In addition, there are several
collaboration services covered such as co-editing or collaborating on a
project. It would probably help if you could convince the authors to provide
a better protocol documentation.
The Eclipse link is more related to co-editing theory, and provides a rather
clear high level explanation on what would need to be implemented for
defining a shared editing extension from scratch.
To sum-up on one side we have an implementation without protocol
documentation, on the other hand we have a theory and no protocol yet ;)
Date: Sat, 14 Oct 2006 03:53:59 +0530
From: Mridul <mridul at sun.com>
Subject: Re: [Standards-JIG] proto-xep: Shared XML Document Editing -
To: Jabber protocol discussion list <standards-jig at jabber.org>
Message-ID: <453011FF.9090408 at sun.com>
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
I think I mentioned this before too - but what the heck :-)
Collaborative editing of files was introduced in Sun java studio more
than 2 years back using our xmpp api and server as the backend
middleware : and was subsequently opensourced more than a year back (the
entire client side implementation) : http://collab.netbeans.org/
features the whole thing.
If I am not wrong , it included some namespace extensions which allowed
for file sharing (entire projects trees if I remember correctly) ,
shared editing ,etc - in the context of a muc : so it allowed sharing of
multiple files with different subsets editing different shared files ,
with ability to pull these changes to local file project at any time ,
'unsharing' a file , etc.
PS : I was not part of that team which designed and implemented this.
Joonas Govenius wrote:
> FYI, I just happened to come accross this link about a shared code
> editing GSoC project:
> Especially the section "Consistency Maintenance" is very interesting
> from out point of view.
> I contacted the author so hopefully we'll get some input from him
More information about the Standards