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 -~----------~----~----~----~------~----~------~--~---
