Lucas crypt

added cryptstorage with tests and scenario.


See merge request !6

modified example provided in cryptstorage.js comments.
corrected error introduced by last commit
(renaming of variable causing errors).
modified tests to comply with cryptstorage.js changes

Master



See merge request !3

Release jIO v3.4.0

Release jIO v3.4.0
------------------

It includes:
- Updated Dropbox Storage @lucas.parsy
- ERP5: support of read_only erp5 field ("your_field")

See merge request !2

- Dropbox storage: update to latest jio
- ERP5: support of read_only erp5 field ("your_field")

This allows to use properties from ERP5 that can be updated locally but won't
be saved by ERP5. eg: your_modification_date allows to obtain the modification date of the
object, but it won't be saved on the Object in ERP5 when updated.

added blob datatype in dropboxstorage getAttachment's ajax request,

to not receive corrupted files

See merge request !1

to not receive corrupted files

when attempting to remove an inexistent document.

added comments in dropboxstorage.js about the Dropbox API limitations.

updated dropboxstorage.tests.js to suit to previous changes in dropboxstorage.js

Never build URL by concatenating strings, as it does not correctly handle escape.

Remove useless requests which will not prevent raise condition.

allowing to choose between "dropbox" (access to full dropbox account)
and "sandbox" (cannot access files not created by the jio application)
mode.

of putattachment method (150MB limit)

works with the new dropbox API.
dropbox storage redesigned to have the same behavior as DAV storage.

This storage will transparently compress getAttachment/putAttachment results.
Only text, json, xml mme type are compressed.

Thanks to Lucas Parsy.

Activate it by adding the 'repair_attachment' parameter in the storage description.
Then, call the repair method.

This was just a prototype, which has been replaced by the replicatestorage.

Configure the storage with the conflict_handling parameter value:
   0: (default): no resolution (ie, throw an Error)
   1: keep the local state
      (overwrites the remote document with local content)
      (delete remote document if local is deleted)
   2: keep the remote state
      (overwrites the local document with remote content)
      (delete local document if remote is deleted)
   3: keep both copies (leave documents untouched, no signature update)