This is especially important for mobile devices. Because OT can be optimistically applied, offline operation seems like a natural fit. It's probably a good idea to provide some "conflict resolution" -- though by design, OT does not generate conflicts.
Wavelets do have a history hash, though it doesn't work exactly like git. David On Oct 8, 7:30 am, nathanaeljones <[email protected]> wrote: > I understand how waves could be created offline, due the GUID id. > However, how could wavelets or documents be safely created offline > without potential ID conflicts? Is there an ID conflict resolution > system? > > Without a recursive hash structure (like git), how could offline > synchronization be performed in a efficient manner? > > Modern e-mail systems are plagued by this problem - without recursive > hashing, checking for new e-mail is much more expensive than comparing > one 128-bit integer. > > A local 'caching' server could be an option for businesses (but not > normal users). Either way, multi-way database synchronization is > needed. > > Are there any docs or plans regarding this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
