I think this is an interesting question, but it should be a lower
priority for now. I guess that Google not only chose to not implement a
delete function for Waves for usability reasons. Implementing something
like a delete function in a distributed system can be very difficult.
For example, what do you do if a participant has been removed from a
Wave, but not all Wave servers have been informed about this (e.g. due
to maintenance)? In this case you have diverging information about a
Wave (should it be deleted or not?). Furthermore, some Wave servers may
send updates for deleted Waves to other Wave servers. Maybe something
like this could work:
1) Participants can unfollow a Wave
2) After some time (up to the Wave server?) they are removed from the Wave
3) Once all participants of one Wave server ("X") have been removed from
the Wave, the Wave server ("X") deletes (achieves?) the Wave locally
after some time (up to the Wave server?), but keeps the ID
4) If updates for a Wave which has been deleted are received by a Wave
server ("Y"), the Wave server ("X") and Wave server ("Y") synchronize
the participant list (i.e. Wave server ("X") informs Wave server ("Y")
that it has no participants in this Wave)
5) after some time Wave server ("X") removes the ID of the deleted Wave
Alternatively, "delete" can also be managed by the Wave server managing
the Wave. However, I hope that Apache Wave will give up this bottleneck
and implement a more dynamic solution.
I may explore this problem in more detail once the migration of the
source code to the Apache web site is complete.
Am 17.05.2011 20:35, schrieb Zachary “Gamer_Z.” Yaro:
IMO there should be some way for a user to "Delete" the wave (i.e. remove
self from participants and unfollow). When all participants have done this
(plus maybe a week to let them undo) it should be okay to delete the wave
and its history.
--Zachary “Gamer_Z.” Yaro
On Tue, May 17, 2011 at 13:06, Lennard de Rijk<ljvder...@gmail.com> wrote:
Hi,
If you are removed from a wave you are allowed to see the state (and
history) up till the point when you got removed.
This is unfortunately not the case yet for the current version of the c/s
protocol. The intention has been documented at the bottom of [0] and works
on wave.google.com iirc.
Greetings,
Lennard
[0]
http://www.waveprotocol.org/protocol/design-proposals/clientserver-protocol
On Tue, May 17, 2011 at 09:56, Michael MacFadden<
michael.macfad...@gmail.com> wrote:
Good points all. I do understand the point of not deleting waves and
keeping the history. One question though. Do we really need to prevent
the
deleting of waves all together. What about a wave that all participants
have been removed? Can it ever be accessed again? What is the point of
keeping it around? I am sure these questions have all been answered
before.
We should probably discuss them and document them.
~Michael
On May 17, 2011, at 9:42 AM, Yuri Z wrote:
You can remove yourself from participants. That's what I do. Or you can
just
delete the _deltas folder.
2011/5/17 Michael MacFadden<michael.macfad...@gmail.com>
All,
Is there a way to delete waves from WiaB? From a development
standpoint
when working on bugs having to do with creating new waves your WiaB
instance
quickly gets polluted with a large number of "test" waves that seem to
hang
around forever unless you blow away your persistence.
I know that in general Google Wave didn't allow you to "delete" waves
from
a user stand point, which makes sense. But at least in some sort of
development mode, would being able to delete waves be useful?
~Michael
