commit | 85b45d38ba0e93201aec4c79e27b388c58f85373 | [log] [tgz] |
---|---|---|
author | Adam Sadovsky <sadovsky@google.com> | Fri May 29 21:57:40 2015 -0700 |
committer | Adam Sadovsky <sadovsky@google.com> | Fri May 29 21:58:14 2015 -0700 |
tree | 5d25449b40cd0c8db6d7c350d970b64fa1ca3224 | |
parent | 1a066a8a75992d436a0c60d5621e944500fbd9b4 [diff] |
syncbase: store log entries chronologically This change makes it easier for clients to iterate over log entries chronologically, which is the common case (both for client watch and for sync watch). Originally I used reverse chronological order because it was more efficient for determining the most recent sequence number (done once, at startup time) - but that's not what we should optimize for. Change-Id: I84879054ed5617f23f8d717e0e363aee12ea2873