On Fri, Sep 04, 2009 at 12:06:49PM -0700, Tad Glines wrote: > 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.
Generally speaking, in my experience the wavelets become un-editable as opposed to inaccessible. > 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? I suspect (???) that only the server that hosts the wavelets keeps the entire history of the wavelet. So if the server goes down you have already lost the history, and forking based on the current version might be the easiest/only solution. At the same time, losing the entire history makes me uneasy. I previously had the alternative suggestion that keeping copies of the data (including history) might be best done at the database level. Semi-related: I read somewhere a suggestion that it should be possible for a user to create a fork of a wave if he/she is removed from the participant list of the wave, from the point where they lost access. If so, this would reduce my concern that some upset person could remove my access to the information I keep in shared waves that I use to (for example) do my job (although the updates I may miss could be just as important). -- Brian May <[email protected]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
