Merge lp:~pedronis/u1db/naming-in-sync-doc-json-envelope into lp:u1db
Proposed by
Samuele Pedroni
Status: | Merged |
---|---|
Approved by: | John A Meinel |
Approved revision: | 138 |
Merged at revision: | 138 |
Proposed branch: | lp:~pedronis/u1db/naming-in-sync-doc-json-envelope |
Merge into: | lp:u1db |
Diff against target: |
63 lines (+7/-7) 3 files modified
u1db/remote/http_app.py (+3/-3) u1db/remote/http_target.py (+2/-2) u1db/tests/test_http_app.py (+2/-2) |
To merge this branch: | bzr merge lp:~pedronis/u1db/naming-in-sync-doc-json-envelope |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
John A Meinel (community) | Approve | ||
Review via email: mp+84180@code.launchpad.net |
Description of the change
use the more consistent naming 'content' not 'doc' for the main data field in the json object entries exchanged by sync for each document, right now we pass documents as strings (because is the natural thing with the current layering of things, and the current Document interface)
To post a comment you must log in.
Thanks. There are still a few places in the code where it would be good to do this. (Eg. u1db.tests. simple_ doc)
I like sending the content as strings, so that we don't change the actual content. It would be nice to preserve:
PUT_DOC(id, content)
sha1(content) == sha1(GET_DOC(id))