diff options
| author | Sascha Silbe <sascha-org-sugar-git@silbe.org> | 2009-07-14 11:25:00 (GMT) |
|---|---|---|
| committer | Sascha Silbe <sascha-org-sugar-git@silbe.org> | 2009-07-14 11:25:00 (GMT) |
| commit | be161642453e1012cdc4978492f603ee57d21c36 (patch) | |
| tree | 777bccc240daa9e8404ecef69e571f4807b55c5b | |
| parent | 26c4681120097b333480a03185481163d034c845 (diff) | |
more TODOs
| -rw-r--r-- | datastore-redesign.html | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/datastore-redesign.html b/datastore-redesign.html index 6d24ef3..e74250e 100644 --- a/datastore-redesign.html +++ b/datastore-redesign.html @@ -25,7 +25,12 @@ <li>examine / define API call interactions, esp. in case we switch to fully synchronous design</li> <li>do we want an optimized way to determine (only) the branch HEADs of a given <code>tree_id</code>?</li> <li>example activity <-> data store interaction</li> - <li>Tomeu: What about having a separate call that returns synchronously a new <code>tree_id</code> and/or <code>version_id?</code></li> + <li>Tomeu: What about having a separate call that returns synchronously a new <code>tree_id</code> and/or <code>version_id?</code> + <ul> + <li>need to handle missing intermediate versions in that case (parent_id set to a never-committed version)</li> + </li> + </li> + <li>cross-<code>tree_id</code> duplicate detection/optimization</li> </ul> <h2>(A)synchronicity of API calls</h2> |