diff options
author | drebs <drebs@leap.se> | 2017-05-04 15:59:47 +0200 |
---|---|---|
committer | drebs <drebs@leap.se> | 2017-05-04 16:16:50 +0200 |
commit | ad065fc8c9204e6d63b7fb69b1d9cf469812237f (patch) | |
tree | 05682fee4ba560aed9f7a224a8e11a95e174deb0 /docs/sphinx/attachments.rst | |
parent | 6008e999eea82bb4355b086453be42414a4d60c9 (diff) |
[doc] add attachments documentation
Diffstat (limited to 'docs/sphinx/attachments.rst')
-rw-r--r-- | docs/sphinx/attachments.rst | 77 |
1 files changed, 77 insertions, 0 deletions
diff --git a/docs/sphinx/attachments.rst b/docs/sphinx/attachments.rst new file mode 100644 index 00000000..098f634f --- /dev/null +++ b/docs/sphinx/attachments.rst @@ -0,0 +1,77 @@ +Document Attachments +==================== + +.. contents:: Contents: + :local: + +The content of a Soledad document is assumed to be JSON. This is particularly +bad for storing larger amounts of binary data, because: + +* the only way to store data in JSON is as unicode string, and this uses more + space than needed for binary data storage. + +* the process of synchronization of Soledad documents depends on completing the + transfer and decryption of the content of all new/updated documents before + synchronized documents are available for use. + +Document attachments were introduced as a means to store large payloads of +binary data and have them be synchronized separate from the usual Soledad +document synchronization process. + +Example +------- + +The attachments API is currently available in the `Document` class, and the +document needs to know about the store to be able to manage attachments. When +you create a new document with soledad, that document will already know about +the store that created it, and can put/get/delete an attachment: + +.. code-block:: python + + from twisted.internet.defer import inlineCallbacks + + @inlineCallbacks + def attachment_example(soledad): + doc = yield soledad.create_doc({}) + + state = yield doc.get_attachment_state() + dirty = yield doc.is_dirty() + assert state == AttachmentStates.NONE + assert dirty == False + + yield doc.put_attachment(open('hackers.txt')) + state = yield doc.get_attachment_state() + dirty = yield doc.is_dirty() + assert state | AttachmentState.LOCAL + assert dirty == True + + yield soledad.put_doc(doc) + dirty = yield doc.is_dirty() + assert dirty == False + + yield doc.upload_attachment() + state = yield doc.get_attachment_state() + assert state | AttachmentState.REMOTE + assert state == AttachmentState.SYNCED + + fd = yield doc.get_attachment() + assert fd.read() == open('hackers.txt').read() + +Implementation +-------------- + +The current implementation of document attachments store data in a separate +SQLCipher database in the client (using SQLite's BLOB type) and in the +filesystem in the server. Encryption of data before it's sent to the server is +the same used by normal Soledad synchronization process (AES-256 GCM mode). + +Document attachment API +----------------------- + +.. autoclass:: leap.soledad.client._document.AttachmentStates + :members: + :undoc-members: + +.. autointerface:: leap.soledad.client._document.IDocumentWithAttachment + :members: + :undoc-members: |