Hi Alex thanks for clarification about the empty document operation.
But what about the calculation of the signature bytes? Do you have any idea how these bytes are calculated? What is the input data for the signature, which algorithms are used etc. I didn't find something in the specs. I only find a detail description how the signer ID is calculated (so I can verify it). So, any hint would be helpful. Regards Johannes On 1 Okt., 02:12, Alex North <[email protected]> wrote: > On 30 September 2010 22:46, jowi <[email protected]> wrote: > > > 1. I think, I understand the structures in operation [1] and operation > > [2] but I don’t understand why operation [0] is used in the > > ProtocolAppliedWaveletDelta message. So what is the reason for sending > > operation [0] with an empty (?) document_operation? > > This looks like an artifact of some leaky abstractions in the wave model > code. OpBasedWavelet.createBlip() sends an empty operation on the blip's > document to ensure its metadata is initialised. Code in the conversation > model then adds content to the blip. The first op is redundant in this case > but it's difficult to just remove. Details of the operations produced by > various mutations and their bundling into deltas are hidden from the model > code that makes the mutations. > > I don't think precise sequences like this would ever appear in a spec. It's > very difficult to specify operation sequences in a wave-like system where > ops from many clients may interleave arbitrarily. We can only specify what > states of the document are valid and what they mean. > > HTH, > Alex -- 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.
