From wave-dev - may be of interest. The "shared live objects" (SLOBs) concept is interesting; I had a look at the source but couldn't figure out what transport was being used for synchronisation (e.g. polling, cometd, websockets...)
S Begin forwarded message: > From: Yuri Z <[email protected]> > Date: 27 October 2011 05:29:22 GMT+01:00 > To: [email protected] > Subject: Re: Walkaround -- Wave on App Engine > Reply-To: [email protected] > > Woot, great news! I am really excited! > > On Wed, Oct 26, 2011 at 9:55 PM, Christian Ohler <[email protected]> wrote: > >> Fellow wavers, >> >> rather than making waves accessible in Google Docs, which takes too >> long, we are releasing our code in a form that will hopefully be >> useful in the short term. You can find it at >> https://code.google.com/p/walkaround/ . >> >> From the project description: >> Walkaround is a variant of Wave, based on the Apache Wave code base, >> that runs on App Engine. Walkaround can import waves from >> wave.google.com to allow users to keep working with their data >> regardless of the future of wave.google.com. (The import feature is >> still experimental.) >> >> Much of the walkaround code is not specific to Wave, but factored out >> as a separate, more general collaboration layer that manages shared >> live objects. These objects can be modified by multiple clients at >> the same time, with changes made by any client immediately broadcast >> to all others. The Wave application is built on top of this, but the >> live collaboration layer is flexible enough to support other >> applications. >> >> Walkaround supports live concurrent rich-text editing, in-line >> replies, user avatars, wave gadgets, attachments, and we are working >> on integrating App Engine's full text search service. For now, it >> does not support Wave robots, federation, or private replies, but >> these features could be added. >> --- >> >> Some of you have been asking about Wave on App Engine; perhaps this is >> what you are looking for. >> >> The Wave application in walkaround depends very heavily on the Apache >> Wave code base, but the general collaboration layer is useful >> independently, so we put it into a separate repository for now. >> >> Happy hacking, >> Christian. >>
