I remember seeing contributor being internally managed within index wave as per fedone implementation.
Have a look at my previous test<http://code.google.com/r/jlee119-wave-protocol/source/browse/test/org/waveprotocol/wave/examples/fedone/waveserver/WaveCreationFunctionalTest.java?spec=svn5a03d78f50977ea7140b9c21cc4e0d03fe399881&r=5a03d78f50977ea7140b9c21cc4e0d03fe399881>line number 47 to see how Index wave is used to maintain contributors for a specific wavelet. I'm not sure how contributors for a specific blip is maintained. I've pull those tests out later because it wasn't part of federation protocol, but internal strategy for wave provider at that time, now I believe it's going to be available from new drop of code. J On 26 May 2010 11:55, "Torben Weis" <[email protected]> wrote: Hi, I had the same problem with QWaveClient several months ago. I learned that the contributor tag must not be used currently. The authors of a blip is the set of wave participants who submitted a delta. In theory each editing user leaves an annotation (see the spec) in the blip. You can use this as well to figure out who was editing and when. However, QWaveClient does not set these annotations and I have doubts that the console client does (at least old versions did not). Cheers Torben 2010/5/26 Vaclav Sykora <[email protected]> > > hi, > > according to Wave Conversation Model 8.4.2 a blip document should have > <contributor> ... -- --------------------------- Prof. Torben Weis Universitaet Duisburg-Essen [email protected] -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group... -- 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.
