It looks like FedOne generates history requests based on applied_at version. So for example, if it's current version is 5 and it receives an update with an applied_at version of 20, then it'll make a history request for the range 5-20 with 5 being inclusive and 20 be exclusive. This will return ProtocolAppliedWaveletDeltas with applied_at version of 5-19.
I'm assuming the Google's live code is using the same semantics. I think the spec needs to be updated to indicate that history requests are for ProtocolAppliedWaveletDelta's with specified applied_at versions. -Tad On Fri, Mar 5, 2010 at 11:38 AM, Tad Glines <[email protected]> wrote: > The spec implies that a history request is for actual versions not > applied-at versions, but the FedOne implementation appears to be returning > ProtocolAppliedWaveletDelta's with hashed_version_applied_at that match the > history request. In WaveletContainImpl.java requestHistory() returns > ProtocolAppliedWaveletDelta from appliedDeltas that match the requested > version range. However appliedDeltas is sorted based on the applied_at > version and not the version-after-application. > > Is this a bug, or am I missing something? > > -Tad > -- 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.
