In the .proto files annotation boundaries are specified as:
message AnnotationBoundary {
...
repeated string end = 2;
repeated KeyValueUpdate change = 3;
}
... And KeyValueUpdate is:
message KeyValueUpdate {
required string key = 1;
// Absent field means that the attribute was absent/the annotation
// was null.
optional string old_value = 2;
// Absent field means that the attribute should be removed/the
annotation
// should be set to null.
optional string new_value = 3;
}
My question: Why have 'repeated string end' in AnnotationBoundary? Why not
just use the change field to change the value to null?
... Or put another way: As an implementor, am I free to use either method to
null out annotations?
-J
--
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.
