Ok, that sounds pretty perfect for my concept then!
I'll look more into your system in the current weeks when I got more time.
I'll probably wait for the java side of things whenever thats ready, as my
previous code (both android and the webapp via gwt) was Java so It will
probably be easier to ada
Hello,
Thomas, you are right. The server has been extended but no so much.
The other part is the client API. You can develop your Web App
(Java/Android very soon) using the API
to manage their data. The app could use any server with the extension. Any
app knowing how is your data model could commu
Can I clarify how this works;
If a few people ran wave servers with this extension, could they federate a
few different data models? (ie, this one extension would allow different
users using wave for different things, and provided other severs have the
same extension, they can all talk to eachother
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 (i
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 wrote:
> Hello,
>
> I would like to introduce something I have been working on during past
> months in the con
