Updates:
Status: WontFix
Comment #7 on issue 34 by btkalman: Client cannot rejoin wave after Wave
Server restart
http://code.google.com/p/wave-protocol/issues/detail?id=34
I say that they don't relate because the bug originally filed seems to
indicate a bug
related to the *client*, but the hosting issue we've been talking about is
entirely a
server issue. However, as you say, it could just be that when this was
filed it was
misinterpreted as a client bug.
Overall this isn't a bug -- the question of whether there should be a way
for a host
to recover its wavelets is something that could be discussed properly on the
wave-protcol discussion, not here. So, I will mark this as closed.
--
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
-~----------~----~----~----~------~----~------~--~---
