Re: Client/Server protocol (again)

2011-07-08 Thread Thomas Wrobel
On 8 July 2011 19:15, Joseph Gentle wrote: > Not true. Or, not true for long. Some people are talking about putting > an open federation spec together: > http://piratepad.net/HET5ojzCXM Talking and getting working code is too different things...and then getting a bunch of others to support the s

Re: Wave documentation

2011-07-08 Thread Yuri Z
Any update on this? It seems like the API documentation is already deprecated, and one day it can be just taken down, while there's a lot of valuable and relevant information for the WIAB project. Can someone from the Googlers to check if some of the Google Wave API documentation can be open source

Re: Client/Server protocol (again)

2011-07-08 Thread Joseph Gentle
Not true. Or, not true for long. Some people are talking about putting an open federation spec together: http://piratepad.net/HET5ojzCXM But thats still not really answering your question. As far as I know, the client-server protocol for wave in a box is pretty stable at this point. Its documente

Re: Client/Server protocol (again)

2011-07-08 Thread Scott Wilson
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. >

Re: Client/Server protocol (again)

2011-07-08 Thread Yuri Z
According to http://incubator.apache.org/wave/people.html Joseph Gentle is listed as committer. 2011/7/8 Joseph Gentle > 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

Re: Client/Server protocol (again)

2011-07-08 Thread Thomas Wrobel
I have to point out, none of these solutions are actually federated - and thus unsuitable for anyone wishing to make a open network where anyone can run a server. Bunchs of individual OT projects are great for specific uses, but for anyone wanting a open network, their not really relevant. WFP is s

Re: Client/Server protocol (again)

2011-07-08 Thread Joseph Gentle
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.