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 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, Oct 27, 2011 at 5:29 PM, Christian Ohler <oh...@google.com> > wrote: > > > > > 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 the situation where a client sends an op, gets disconnected > > > without knowing if the server received it, then reconnects? How can > > > it tell whether to re-send the op? > > > > > > Walkaround solves this by assigning a random client id to each client > > > and storing that together with each op. That way, when the client > > > reconnects and catches up with the ops that happened in the meantime, > > > it can recognize its own ops; and the server can detect duplicate > > > submissions from the same client at the same version. > > > > > > Christian. > > > > > > > > > > > -- > > --Matt > > > -- --Matt
