This project is read-only.

Development Plan

Oct 17, 2009 at 8:19 AM
Edited Oct 17, 2009 at 8:27 AM

I was going to wait till Google releases the source code for their web client but I think there's enough material to get started.

This is the development plan I had in mind

In order of priority

* Part 1 - Wave Server

* Part 2 - Basic Wave Client

* Part 3 - Extensions (Robot API and Gadget)

Gadgets should be compatible since they are written in JavaScript and xml



* Part 4 - Full Web GUI

This would be


Would it be great if we finish this before Google does? That would make history.

Oct 17, 2009 at 11:29 AM

I've been thinking about the server part some more, and I think it's best to first create a fully functional server implementation. After that's complete it's a lot easier to infer a decent API from that. Can anyone compile a list of work items that we'll need to complete for each of the products? That way I think we have a good guideline on what to work on.

Nov 3, 2009 at 11:26 AM

But..... just to ask: why server first????

Building a new server solution It would take a lot of time where we have a full functional server solution already available and ready to rock??

So.... client first, in my opinion, it's the best approach, even because it could be done without a so huge working community.

Cheers all


Nov 3, 2009 at 12:18 PM

Server or Client, they both rely on the same underpinnings, once we have the basic XMPP/WCF Library, we can build a server and client at the same time

Nov 3, 2009 at 1:24 PM

So, the plan is to build a WCF Wave Transport Channel and start to build from this brik??


Nov 3, 2009 at 2:19 PM

Yes, see this thread

Nov 5, 2009 at 1:49 AM

We are going to start a discussion on Google wave, do you guys all have access now?

Nov 5, 2009 at 8:11 AM

Yes, im

Nov 5, 2009 at 6:26 PM

Nope, sorry... Hopefully it would be asap.