waveclient.py: an Open Source wave server-client protocol implementation

[Silicon Dragon]

Dear Wave API users,

On the Begging for the Wave Client protocol specs wave, Lars wrote:

"...We just don't have the resources to work on a stable server-client protocol right now, much as we'd love to and much as we are aware what wonderful things could come out of such a thing.

If others in the open source community start an effort like that we will take part best we can and consider then supporting such a protocol ourselves.

For now, all our efforts (and then some!) are going towards the server-server protocol, which still needs lots and lots of work. (Including open sourcing a lot more of our code to make it realisitc for others to build wave systems...) ."

Seeing how there is a considerable developer interest, we have started an open source effort to create a native python implementation of the Google Wave server-client "protocol".

The goal of the project is to reproduce the most common operations available to all web clients: wave reading, channel stream reading, and possibly writing later on.

(To clarify here: the "protocol" is the JSON mess via which browsers are currently communicating with the Google Wave servers -this way, no extra efforts from the Wave team is necessary)

This is a non-official implementation; as the protocol is subject to changes, it might be broken, or unavailable at any time; but we will make a best effort in keeping it up-to-date with the latest developments.

Sources, and Issue tracker available via github; licensed under BSD.

We are looking for volunteers! If you have a cool project idea, which the current limitations of the available wave APIs doesn't allow for, or want to extend a project of yours, see the proto wave.

-SDr

[Daniel Danopia]

Hey,

I'd appreciate it if the protocol could be documented on a wiki
(insert shameless plug for http://wavecompass.net/) so that I can come
along and write implementations in other languages such as Ruby.

Thanks!
--danopia

On Dec 1, 3:36 am, Silicon Dragon <sdr...@gmail.com> wrote:
> Dear Wave API users,
>
> On the Begging for the Wave Client protocol

> specs<https://wave.google.com/wave/#restored:wave:googlewave.com!w%252B5445...>wave,
>
> Lars wrote:
>
>  *"...We **just** don't have the resources to work on a stable server-client

>
> > protocol right now, much as we'd love to and much as we are aware what

> > wonderful things could come out of such a thing.*
>
> *If others in the open source community start an effort like that we will

> take part best we can and consider then supporting such a protocol

> ourselves.*
>
> *For now, all our efforts (and then some!) are going towards the

> server-server protocol, which still needs lots and lots of work. (Including
> open sourcing a lot more of our code to make it realisitc for others to

> build wave systems...)** ."*
>
> Seeing how there is a considerable developer interest, we have started an *open
> source* effort to create a native python implementation of the Google Wave

> server-client "protocol".
> The goal of the project is to reproduce the most common operations available
> to all web clients: wave reading, channel stream reading, and possibly
> writing later on.
>
> (To clarify here: the "protocol" is the JSON mess via which browsers are
> currently communicating with the Google Wave servers -this way, no extra
> efforts from the Wave team is necessary)
>
> This is a non-official implementation; as the protocol is subject to
> changes, it might be broken, or unavailable at any time; but we will make a
> best effort in keeping it up-to-date with the latest developments.
>

> Sources <http://github.com/waverz/waveclient>, and Issue
> tracker<http://github.com/waverz/waveclient/issues>available via
> github; licensed under BSD.
>
> *We are looking for volunteers!* If you have a cool project idea, which the

> current limitations of the available wave APIs doesn't allow for, or want to
> extend a project of yours, see the proto

> wave<https://wave.google.com/wave/#restored:wave:googlewave.com!w%252B_7o7...>
> .
>
> -SDr