---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23166/#review47507
---
Ship it!
Committed as b77f7f5..5abfce6
Please close the review req
On 07/09/14 16:25, Thomas Wrobel wrote:
Of what benefit would contributing this to wave be?
Doesn't wave do a superset of this functionality already? (albeit with
messier code)
In a similar way to XML being a superset of JSON (and Wave includes bits
that *neither* does well or indeed at all).
Thomas,
That's the key - if the coding model isn't right, the apps and the data
model will never take off. We'll continue to see proprietary dead-end after
dead-end.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: google.com/+JohnBlossom
On Wed, Jul 9, 2014 a
田传武 ,
I am very grateful for your contributions of these libraries. You are
striking at the fundamental blocking point in Wave development- the
existing platform is not well adapted to creating a variety of responsible
apps using a common data model. My mission is to get not only real-time
configu
Of what benefit would contributing this to wave be?
Doesn't wave do a superset of this functionality already? (albeit with
messier code)
Seems (possibly) more useful for Wave to contribute its (federation)
functionality to this or a fork of it. Then you would have a new
pseudo-wave that does much
inline
On Wed, Jul 9, 2014 at 4:43 PM, Christian Grobmeier
wrote:
> What are your plans with it?
>
Not sure, may depend on the feedback.
> Are you considering to contribute this to Wave?
>
I've read most of wave's code, but when I try to do big refactor, I am
baffled.
This looks like awesome work.
What are your plans with it?
Are you considering to contribute this to Wave?
On 8 Jul 2014, at 8:07, 田传武 wrote:
Hi all,
I'd like to share an open-source project which implements nearly all
features of the google drive realtime api. *Google Drive Realtime API*
<
