This is great. I'm especially looking forward to the "code implementing some abstract concurrent data types based on wave documents".
Is there anything helpful you can tell us about this new code that isn't readily deducible from the unit tests? A brief overview of the top level pieces and how they are intended to be used might help accelerate the learning process. -Tad On Sat, Mar 27, 2010 at 2:23 PM, J.D. Zamfirescu <[email protected]> wrote: > Hello everyone, > > We have just open sourced a significant new chunk of Google Wave > source code: the wave document model. The new code, some thirty-eight > thousand lines of code mainly in the > org.waveprocotol.wave.model.document package, implements useful and > efficient data structures for reading and manipulating wave documents. > This is the same document model used by the Google Wave client and > servers. This code is available at: > http://code.google.com/p/wave-protocol/ > > On top of this, we're continuing to work to open source more code. In > the near future we expect to release code implementing some abstract > concurrent data types based on wave documents, which are in turn the > basis for an implementation of the Google Wave conversation model > (http://www.waveprotocol.org/draft-protocol-specs/wave-conversation-model). > The code implementing the wave data models is a pre-requisite for the > release of other components built on these models, including many > components of the web client. The example wave server, FedOne, does > not yet make use of the new code but we intend to update it as a > useful reference (your help welcome!). > > This open source release has taken longer than we wished and > originally planned for, but we're learning as we go. We're now > changing our approach so as to better inform and engage with you, the > wave protocol community, by publishing code earlier: before we're > completely happy with it, before it's "done". That means that this and > future chunks of code are very much works in progress. It does not yet > implement the ideal solution. You can expect to see the code, data > format, and APIs evolve as Google Wave and the protocol evolve. We > can't yet promise stability or backwards-compatibility but are working > towards those goals. We will communicate progress as we work together > along the way. We want to be more transparent and are releasing this > code, warts and all, so it can be most useful to the community. > > We hope you enjoy the new code, and that to come. We look forward to > hearing your feedback and, of course, contributions are welcome. > > Happy waving, > > Alex North and J.D. Zamfirescu-Pereira, for the Google Wave team > > -- > 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. > > -- 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.
