On 8 July 2011 19:15, Joseph Gentle <[email protected]> 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 same system is another step. I wish them luck, but Id rather stick with whats here and now till theres working superior alternatives. > As far as I know, the client-server protocol for wave in a box is > pretty stable at this point. Its documented here: > http://www.waveprotocol.org/protocol/design-proposals/clientserver-protocol > ... Though that documentation is probably out of date. It was my understanding it wasnt yet implemented? There was an older thread here about it; http://mail-archives.apache.org/mod_mbox/incubator-wave-dev/201105.mbox/%[email protected]%3e David Hearnden there said; "I would strongly encourage not building too much on the current protocol, since it has a number of known limitations. The new protocol is simpler and achieves a better separation of functionality. " Which put me off doing a anything with the code as-is. Has this changed now? > > Sad to say it, but the real spec for wiab is the code. > > The client and server talk by sending protobuf messages encoded as > JSON over a socket.io connection. Protobufs are quite formally defined > - so you can see what the messages look like by looking at a few > files in the repository: > > The RPC wrapper: > http://code.google.com/p/wave-protocol/source/browse/src/org/waveprotocol/box/server/rpc/rpc.proto > > The meat: > http://code.google.com/p/wave-protocol/source/browse/src/org/waveprotocol/box/common/comms/waveclient-rpc.proto > http://code.google.com/p/wave-protocol/source/browse/src/org/waveprotocol/wave/federation/federation.protodevel > Those links are really helpfull, however, thanks > The encoding to JSON uses this project: > http://code.google.com/p/protobuf-java-format Already using it :) > > If you care about the client/server API enough to dig through the > code, writing up some proper documentation describing what you find > would be great. Id be happy to - but that might be overestimating my skills somewhat. My java skills uptill now have purely been GWT or Android based stuff. Haven't ever done any server stuff, and the wiab code is a rather steep learning curve every time I try getting to grips with bits of it. -Thomas
