Oh, Goodow is really cool!

The difference is that my API implementation is pure Wave, so it works on
the federated/distributed infraestructure and it inherits the participants
model. These aspects are what we would like to keep and why we like Wave.

Apart from that, Goodow OT data type is JSON (instead of XML) and uses new
technologies like vertx...  and also it provides iOS and Android clients
-but we are going to provide a Java/Android client soon-.

Personally I think the federation protocol and participation model are the
strongest features of Wave today, as long as UIs has become more powerful
and new team-collaboration tools are emerging.

Thank you for the reference Yuri.




2014-12-03 9:31 GMT+01:00 Yuri Z <vega...@gmail.com>:

> Interesting, how does it compare to
> https://github.com/goodow/realtime-store?
> Which I believe is based on walkaround  OT implementation.
>
> On Tue Dec 02 2014 at 1:09:55 AM Pablo Ojanguren <pablo...@gmail.com>
> wrote:
>
> > Hello,
> >
> > I would like to introduce something I have been working on during past
> > months in the context of my current job.
> >
> > I have developed *a generic JavaScript API working on top of Wave*. It's
> > quite similar to the Google Real-Time API, providing similar observable
> > data types: maps, lists and strings.
> >
> > The API works right now but it needs some work to become a fully usable
> > API, for example to add OAuth...
> >
> > It also would be valuable to add a customizable search index to query the
> > shared data models.
> >
> > Source code can be found at: *https://github.com/P2Pvalue/incubator-wave
> > <https://github.com/P2Pvalue/incubator-wave>*
> > The README.md file provides a basic user guide to install and use the
> API.
> >
> > Of course any kind of comments are welcome.
> >
> >
> > Regards,
> >
> > Pablo
> >
>

Reply via email to