Comment #5 on issue 34 by btkalman: Client cannot rejoin wave after Wave Server restart http://code.google.com/p/wave-protocol/issues/detail?id=34
This is expected. If a server restarts then it loses the information about all wavelets (no persistence). If the server wasn't the host then it's fine, it will get an update from the host, realise it's missing the history, then request it (and persistence would allow the server to preemptively request the history). However if the server was the host of the wavelet then the same thing can't happen, there isn't a way for the host to request its own history from remote servers. Again, need persistence. In any case, this doesn't actually seem to relate to the original reported client bug. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
