On Mon, Jul 30, 2012 at 4:34 PM, Nick Santos <
nicks...@google.com> wrote:
> If the Docs people wanted to do this, I think the technical barriers
> would be very difficult (think O(eng years)). Without going into
> technical detail, the stack of components it depends on is deep,
> including a substantial server-side component.
In terms of minimizing dependencies, one partial solution would be to
just not open source any of the server side code. This has been done
in a few other places in closure-library (eg: BrowserChannel,
protobuf, etc) and the community has stepped in to fill the gap with
third_party implementations.
I think part of the complexity you are referring to is the server side
OT component needs to perform the exact same transformations [1] as
the client side code (though I could be misunderstanding why else the
editor would need to be tightly coupled with the server side code). If
it helps getting kix open sourced, I know that I would invest a
significant amount of time into documenting/re-implementing a server
side component. I'm guessing others on this list may be interesting in
doing the same. By using documentation/code examples from how OT works
in Apache Wave we might be able to further minimize the work required.
-Andy
1)
https://groups.google.com/d/topic/closure-library-discuss/GhiycGt0ZH4/discussion