Hi,
Interestingly, there is still a potential issue if you don't reuse session
IDs:
Client: submit op X at version 100
client detects network error, but server does not
Client: Reconnect
Server: Ok. 10 new ops since you connected
Client: submit op X' at version 110
Server gets op X at
On Mon, Oct 31, 2011 at 09:10, Torben Weis torben.w...@gmail.com wrote:
Hi,
Interestingly, there is still a potential issue if you don't reuse session
IDs:
Client: submit op X at version 100
client detects network error, but server does not
Client: Reconnect
Server: Ok. 10 new ops since
If you want to resubmit, then resubmit the exact same version, i.e.
repeat X at version 100.
Never say never :) Wave's design is that servers reject operations
that target a version that is too far below the current version, to
force the client to do the (potentially expensive) transform.
On Mon, Oct 31, 2011 at 13:48, Torben Weis torben.w...@gmail.com wrote:
However, we could argue that a client that is able to remember its ops is
as well able to remember (and reuse) its client id. Thus a
resubmission is easy to identify:
compare the tuple (client-ID,applies-at-version).
Yes,
I just wondered what happens when we add HTML5 and persistent storage
to the mix.
A user opens the wave web page in his browser, eventually it fails to
send the op to the server. So it persists the op
in the local storage. It must persist the client ID as well.
The user closes the browser.
Later
Oh dear. Two tabs - I didn't think of that. What was that quote - the
no plan survives contact with web browsers?
How do multiple tabs interact with local storage? How would a second
tab differentiate between ops in localstorage because the browser
crashed, vs ops in localstorage because an
Yeah, I also stumbled on it. probably need to add .sh and .bat scripts to
run the update for the first time.
Anyway, I also set up demo sintance at https://wavereactor.appspot.com
I am going to enable billing on it as well.
On Fri, Oct 28, 2011 at 6:15 AM, Christian Ohler oh...@google.com wrote:
I wonder if its wire protocol can be made compatible with sharejs
+1
From: Joseph Gentle jose...@gmail.com
To: wave-dev@incubator.apache.org
Sent: Thursday, 27 October 2011, 23:02
Subject: Re: Walkaround -- Wave on App Engine
Hey, awesome.
I wonder if its wire
Thomas dt01pqt...@yahoo.com wrote:
I wonder if its wire protocol can be made compatible with sharejs
+1
From: Joseph Gentle jose...@gmail.com
To: wave-dev@incubator.apache.org
Sent: Thursday, 27 October 2011, 23:02
Subject: Re: Walkaround -- Wave on App
be made compatible with sharejs
+1
From: Joseph Gentle jose...@gmail.com
To: wave-dev@incubator.apache.org
Sent: Thursday, 27 October 2011, 23:02
Subject: Re: Walkaround -- Wave on App Engine
Hey, awesome.
I wonder if its wire protocol can
...@gmail.com
To: wave-dev@incubator.apache.org
Sent: Thursday, 27 October 2011, 23:02
Subject: Re: Walkaround -- Wave on App Engine
Hey, awesome.
I wonder if its wire protocol can be made compatible with sharejs.
-J
On Thu, Oct 27, 2011 at 6:55 AM, Christian Ohler oh
On Sat, Oct 29, 2011 at 8:20 AM, Christian Ohler oh...@google.com wrote:
What are sequence numbers needed for? Do sharejs clients submit
additional operations before the server has acknowledged the first
rpc? Walkaround clients do not, each client has only one submitdelta
rpc (one batch of
Christian
I have some questions regarding settings in runant.sample:
What values should I substitute for your-oauth-client-id and
your-oauth-client-secret? I guess it's the same valuesas for Wave robot
registration? https://wave.google.com/wave/robot/register
Besides that the only issues were:
1.
Thanks so much guys. I'm glad you finally got it out there, and a little
regretful that I didn't do more to help you.
'grats on the launch.
Alex
On Thu, Oct 27, 2011 at 6:55 AM, Christian Ohler oh...@google.com wrote:
Fellow wavers,
rather than making waves accessible in Google Docs, which
@incubator.apache.org
Sent: Thursday, 27 October 2011, 13:14
Subject: Re: Walkaround -- Wave on App Engine
Thanks so much guys. I'm glad you finally got it out there, and a little
regretful that I didn't do more to help you.
'grats on the launch.
Alex
On Thu, Oct 27, 2011 at 6:55 AM, Christian
October 2011, 15:32
Subject: Re: Walkaround -- Wave on App Engine
* Wave wasn't promoted or advertised and most peoples experience off
if consisted of one client while it was buggy. Almost all criticism is
off the client, in fact.
These conversations are old hat.
I needed a federated, open
Subject: Re: Walkaround -- Wave on App Engine
* Wave wasn't promoted or advertised and most peoples experience off
if consisted of one client while it was buggy. Almost all criticism is
off the client, in fact.
These conversations are old hat.
I needed a federated, open, realtime updating system
Christian, Dan, great to see this released!
On Wed, Oct 26, 2011 at 12:55 PM, Christian Ohler oh...@google.com wrote:
Fellow wavers,
rather than making waves accessible in Google Docs, which takes too
long, we are releasing our code in a form that will hopefully be
useful in the short term.
Indeed, this is great to see.
On Thu, Oct 27, 2011 at 10:58 AM, Dan Peterson dpeter...@google.com wrote:
Christian, Dan, great to see this released!
On Wed, Oct 26, 2011 at 12:55 PM, Christian Ohler oh...@google.com
wrote:
Fellow wavers,
rather than making waves accessible in Google
Yuri,
Go to https://code.google.com/apis/console and you can get the client ID
and secret.
Use /authenticate as the OAuth callback.
Got this up and running and it's looking good ;) Great job guys!
Perhaps what Wave needs is a different application to show its potential.
(Something like
darkfl...@gmail.com
To: wave-dev@incubator.apache.org; Paul Thomas dt01pqt...@yahoo.com
Sent: Thursday, 27 October 2011, 16:55
Subject: Re: Walkaround -- Wave on App Engine
, it was nothing to do with advertising or just about the client.
My point was thats its relative success did have to do
Thanks everyone for the feedback! There were a few questions that I can answer:
On Thu, Oct 27, 2011 at 04:58, Jérémy Naegel jeremy@gmail.com wrote:
One question: Does this mean that the Wave-in-Docs project is fully
cancelled?
The team that was building Wave in Docs decided to build Wave
On Thu, Oct 27, 2011 at 15:02, Joseph Gentle jose...@gmail.com wrote:
I wonder if its wire protocol can be made compatible with sharejs.
I took a brief look at
https://github.com/josephg/ShareJS/wiki/Wire-Protocol and the
protocols seem to be designed a bit differently. How does sharejs
handle
This might now be a little off topic, but I wanted to write a quick note
that I'm working on setting up a demo instance..
I'll let folks know once I've had success..
On Thu, Oct 27, 2011 at 5:29 PM, Christian Ohler oh...@google.com wrote:
On Thu, Oct 27, 2011 at 15:02, Joseph Gentle
Cool (and sounds perfectly on topic to me!)
On Thu, Oct 27, 2011 at 6:14 PM, Matt Richards mricha...@gmail.com wrote:
This might now be a little off topic, but I wanted to write a quick note
that I'm working on setting up a demo instance..
I'll let folks know once I've had success..
On Thu,
Only snag in this right now, is I can't seem to figure out how to get it to
authenticate to AE. There isn't a lot of information to work work with
(yet).
On Thu, Oct 27, 2011 at 8:26 PM, Dan Peterson dpeter...@google.com wrote:
Cool (and sounds perfectly on topic to me!)
On Thu, Oct 27, 2011
Is ant deploy giving you an error? Try something like
appengine-sdk/*/bin/appcfg.sh update build/war
This is from memory, I'm not at my machine, but I hope it helps you
figure it out.
Christian.
On Thu, Oct 27, 2011 at 18:32, Matt Richards mricha...@gmail.com wrote:
Only snag in this right now,
Fellow wavers,
rather than making waves accessible in Google Docs, which takes too
long, we are releasing our code in a form that will hopefully be
useful in the short term. You can find it at
https://code.google.com/p/walkaround/ .
From the project description:
Walkaround is a variant of Wave,
Woot, great news! I am really excited!
On Wed, Oct 26, 2011 at 9:55 PM, Christian Ohler oh...@google.com wrote:
Fellow wavers,
rather than making waves accessible in Google Docs, which takes too
long, we are releasing our code in a form that will hopefully be
useful in the short term. You
29 matches
Mail list logo
