It should - the algorithms are the same. Whether or not it actually works is another matter. I keep accidentally breaking ShareJS's reconnection logic through tiny oversights.
-J On Wed, Jun 12, 2013 at 4:51 PM, Zachary “Gamer_Z.” Yaro <zmy...@gmail.com> wrote: > I am pretty sure that was what was happening. I know I used to edit waves > on my laptop on the bus (where there was no Internet connection) and ignore > the “Unsynced waves” message. When I got where I was going and connected > to the Internet, my waves would automatically sync and the warning would go > away. I never got to see how conflicts were handled though, and I do not > know if WIAB does the same thing. > > > —Zachary “Gamer_Z.” Yaro > > > On 12 June 2013 17:46, Bruno Gonzalez (aka stenyak) <sten...@gmail.com>wrote: > >> On Wed, Jun 12, 2013 at 11:43 PM, Michael MacFadden < >> michael.macfad...@gmail.com> wrote: >> >> > when the client goes >> > offline, you can still edit. Operations are queued and then sent to the >> > server when it is connected again. >> > >> >> Ah. Is this what really happened behind the curtains when the >> googlewave.comclient showed the "syncing" (or similar) message on a >> corner? (I think wiab >> may also do this too?) >> >> -- >> Saludos, >> Bruno González >> >> _______________________________________________ >> Jabber: stenyak AT gmail.com >> http://www.stenyak.com >>
