Deleting the child of the rootBlip will not delete it's "children" (the rest of the conversation). This may be a bug. Of course, I'm guessing that his application wants that update to be immediate, so that he can post other data in the blip and then allow people to respond to it. He could lock the blip (delete all event blips until the rootBlip deletes the conversation) though.
On Nov 21, 11:44 pm, qMax <[email protected]> wrote: > In any case, you first need some event to trigger your action. > > If i recall properly, in event context you can always get root blip of > wavelet, and direct children of affected blip. > Then you can try following: > 1. modify the root blip with dumb data (say, some special annotation > at start). > 2. catch on_blip_submitted event on root blip. (check your dumb data > to assure it is your modification) > 3. now you have access to all children blips of root. > 4. delete all direct children with all their descendants > 5. remove dumb data from root blip. > > On Oct 28, 8:44 pm, shitu <[email protected]> wrote: > > > > > Hi all.. > > I wants to delete all the blips in the wave except the root blip. -- You received this message because you are subscribed to the Google Groups "Google Wave API" 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/google-wave-api?hl=.
