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)

This shows how to use localstorage, indexedDB, dav, replicate.

This allow to not check the document in the second step of synchro.

Array parameters are converted to multiple FormData.append calls.

Definition is done by a jIO.allDocs query

portal_type and parent_relative_url properties are required.

This only stores properties editable on the default document view.

view attachment only works if default_view_reference is specified during the storage creation.

Synchronisation status is based on document signature (sha) comparison.
Signature are stored each time a document is successfully synchronised.

Conflict are detected but reported as an error for now, as no solve process is implemented.

This (slow) method will be used to stabilised a storage (launch synchronisation process for example).

Use a new optional parameter: jIO.getAttachment(id, name, {format: blob})

Supported formats are: blob, text, json, array_buffer, data_url

Do not return the list of attachments in jIO.get.
Use a specific "allAttachments" method to fetch this information.

jIO.get now really returns the document as saved by jIO.put/post.