I presume the rest of the setup is exactly the same as it has been for FedOne?

On Thu, May 27, 2010 at 11:53 AM, Joe Gregorio <[email protected]> wrote:
> On Thu, May 27, 2010 at 2:39 AM, J.D. Zamfirescu <[email protected]> wrote:
>> Hi group!
>>
>> We've just pushed a first working version of our Simple Web Client,
>> complete with our Rich Text Editor integrated and an updated FedOne
>> that speaks the draft client-server protocol. This code lives in the
>> branch "io2010", available here:
>> http://code.google.com/p/wave-protocol/source/checkout?repo=io2010
>>
>> We wanted to get this code out to you as soon as possible, despite
>> some (very) rough edges. The code we've pushed is functional and
>> federates with wavesandbox.com, but there are a number of caveats.
>>
>> First, here is what we're releasing today:
>>
>> • The Wave Rich-Text Editor
>
> Just as a note, the before you run the new FedOne for the first time
> you need to:
>
> $ ant compile_gwt
>
> Which will build the JS for the editor.
>
>   Thanks,
>   -joe
>
> --
> Joe Gregorio
> Developer Relations, Google Wave
>
>> • A client-side concurrency control module (aka "CC stack"), which
>> coordinates the communication of deltas between a Wave client and a
>> Wave server.
>> • A Simple Web Client that combines the Rich-Text Editor and CC stack
>> together with a simplistic "login" system and wave selection panel.
>> (If you're familiar with FedOne, think of this as the web version of
>> the FedOne console client, albeit with real-time editing.)
>> • An updated FedOne that serves the new client-server protocol and
>> hosts the simple web client.
>>
>> All this code requires GWT on the client, so we've added GWT to the
>> mercurial repository. Once you have run the new FedOne server, by
>> default the new web client will be available on port 9898. The web
>> client requires a browser that supports WebSocket - currently Chrome
>> and Webkit nightly builds.
>>
>> Next, the caveats:
>>
>> • The Simple Web Client uses the new conversation model but only
>> implements a very basic subset of its features: a single root thread
>> and its component blips.
>> • The client-server connection remains fragile - the CC stack supports
>> handling reconnecting when the underlying connection drops, but we
>> haven't yet hooked up this logic, and the FedOne server doesn't
>> support it well yet.
>> • The index wave (the equivalent of the "inbox" in FedOne) still uses
>> an older version of the Wave model.
>> • Tests are broken all over the place. This is unfortunate, but we're
>> aware of it, and are committed to fixing them. We just wanted to
>> release this code ASAP. Fixed tests to follow.
>> • The client-server protocol has been changed, but still isn't in it's
>> final form. We'll be making more changes to it in the near future.
>>
>> Once the above issues have been addressed, we'll be moving the code to
>> the main repository - for now, development will be in the open on the
>> io2010 branch. Stay tuned for fixes to these issues soon.
>>
>> Happy hacking!
>>
>> Anthony Baxter and J.D. Zamfirescu
>> Google Wave
>>
>> --
>> 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.
>
>



-- 
--Matt

-- 
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.

Reply via email to