On Sat, Jul 9, 2011 at 8:19 AM, Thomas Wrobel <darkfl...@gmail.com> wrote: >> 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/%3cbanlktimi_a6zkpsrxqqvhwysrfhh35-...@mail.gmail.com%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?
I don't know - I haven't been working with the wave in a box code for the last 6 months or so. >> 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. I worked with the wave / wave in a box code for about half a year, and I still feel like that whenever I dive in there. Despite referring to (& editing) those protobuf files maybe a dozen times, it still took me 5-10 minutes to find them again. You can still get work done with that feeling, but it is slow going. If you want a good client/server protocol for wiab, familiarise yourself with the WIAB code and implement those changes Hearnden was talking about. -J > -Thomas >
