On 8 Jul 2011, at 17:27, Joseph Gentle wrote: > Heh - that looks like sharejs: > https://github.com/josephg/ShareJS/ > > I don't have a committee, but I've got OT-based syncronization of > arbitrary JSON objects working. So you can write web apps and keep > complex data structures synced up. > > There's a lot of little OT projects popping up at the moment. I don't > think you're alone in fleeing from fedone's code base.
Yep, I've made one of those too (also Node+Redis): https://github.com/scottbw/wave-node :-) S > > -J > > On Thu, Jul 7, 2011 at 4:31 AM, Rohit Rai <rohitb...@gmail.com> wrote: >> Hi Guys, >> >> I haven't been able to invest much time on wave... found it the code too >> cumbersome to work with... but thats a long rant I won't bother with. >> >> I just keep tabs on the development of the project. I was only interested in >> the OT part of it and it was not documented and lack of documented >> client/server protocol didn't help! GWT was the final deal breaker :D >> >> But when I left wave for and started looking for something else, I found >> many things on the way... but the one that took my attention was >> http://opencoweb.org/ >> >> An OT framework, both for Python and Java with a lot of documentation and a >> well defined Javascript client API and a proper documented client/server API >> based on Bauyex. >> >> I hope it can help to establish a good client server protocol base for >> others too. >> >> Regards, >> Rohit >> >> The diamond cannot be polished without friction, nor man perfected without >> trials >> http://mytechrantings.blogspot.com >> >> >> On Wed, Jul 6, 2011 at 9:29 PM, Thomas Wrobel <darkfl...@gmail.com> wrote: >> >>> I wondered if there was any interest again in helping push forward a >>> stable client/server protocol for wiab? >>> >>> A few weeks back there was a thread started >>> ( >>> http://mail-archives.apache.org/mod_mbox/incubator-wave-dev/201106.mbox/thread >>> ), >>> which then developed into a interesting discussion on protocols for >>> wave (and wave-like) systems in general. >>> >>> However, the original intention (at least, from my perspective) of >>> trying to push for a simple c/s interface for wiab...allowing anyone >>> to write a client and connect to any standard wiab server.....seemed >>> to have been lost. >>> So I wondered if anyone was up for trying to work on it? I'm willing >>> to help out as much as I can - although I'm mostly a java client >>> coder, with little knowledge of the inner code of wiab. I could mock >>> up basic clients to test the protocol with a lot easier then making >>> wiab modifications. However, in either case, I'm willing to learn and >>> put in the time if it means getting this functionality added. >>> >>> I'm assuming any c/s for wiab will be still based around there proposal >>> here; >>> http://www.waveprotocol.org/protocol/design-proposals/clientserver-protocol >>> >>> -Thomas Wrobel >>> arwave.org >>> >>> >>> >>> ~~~~~~ >>> Reviews of anything, by anyone; >>> www.rateoholic.co.uk >>> Please try out my new site and give feedback :) >>> >>
