Well, it describes the messages that go between a client and server. If you want a description of what a client should actually do with the messages, well we don't have that. But we do have code in org.waveprotocol.wave.concurrencycontrol (which will largely stay the same in the new protocol).
A. On 25 November 2010 22:22, Nathanael Abbotts <[email protected]> wrote: > Thanks Alex! I'd seen that doc, but thought it only described the server > side operations. Am I wrong? > -- > Nathanael Abbotts > > Email: [email protected] > Wave: [email protected] > Twitter: @natabbotts (http://twitter.com/natabbotts) > > > > On Thu, Nov 25, 2010 at 22:19, Alex North <[email protected]> wrote: > >> Hi Nathanael, >> >> The current protocol is poorly documented ( >> http://wave-protocol.googlecode.com/hg/whitepapers/client-server-protocol/client-server-protocol.html) >> and not fully implemented by WIAB. I'm working towards a new protocol, which >> is outlined here: >> http://www.waveprotocol.org/protocol/design-proposals/clientserver-protocol >> >> Work on this has been held up by some clean-ups that had to come first, >> but that's mostly complete now. Note that that document is a proposal rather >> than a spec, and I expect minor changes (which will be discussed on this >> forum). >> >> I'm glad you're interested in building a client - please post here if you >> have specific questions in the future. >> >> A. >> >> On 25 November 2010 22:13, Nathanael Abbotts <[email protected]>wrote: >> >>> Is there any documentation describing how a client should communicate >>> with a server? >>> I'm working on an alternative (desktop) client, and I need to know what I >>> should be sending/receiving from the server. >>> >>> Thanks, >>> >>> Nathanael Abbotts >>> -- >>> Email: [email protected] >>> Wave: [email protected] >>> Twitter: @natabbotts (http://twitter.com/natabbotts) >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Wave Protocol" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]<wave-protocol%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/wave-protocol?hl=en. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Wave Protocol" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<wave-protocol%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/wave-protocol?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
