Since each delta must be processed by the federation host prior to submitting the next delta, this implies that a wavelet becomes un-editable (at best) or inaccessible (at worst) if the federation host goes offline. Caching in the federation remotes will alleviate the inaccessibility.
If a host goes offline temporarily that's just an inconvenience and isn't a major issue (except for the provider). But if a host suffers a permanent loss, or simply closes shop. All hosted wavelets would become inaccessible. Is it intended that in this situation participants simply fork the wavelet? Or will there be some future protocol version that allows for manual or automatic transfer of ownership to another server? -Tad --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
