more update for the interface CEGA/LEGA

docs/connection.rst

@@ -124,13 +124,13 @@ LocalEGAs can use what message format they see fit.
 The message arriving in the ``v1.files`` queue contains the following fields
 
 * ``user``
-* ``filepath``
+* ``file_path``
 
 The message arriving in ``v1.files.completed`` (from LocalEGA instances) must contain:
 
 * ``user``
-* ``filepath``
-* ``checksums``, as an array of JSON object with:
+* ``file_path``
+* ``decrypted_checksums``, as an array of JSON object with:
 
   - ``type`` (md5 or sha256)
   - ``value``
@@ -140,15 +140,21 @@ The md5 should be present since it is used to compute the stable ID.
 The message arriving in ``v1.stableIDs`` contains:
 
 * ``user``
-* ``filePath``
-* ``stableId``
-* ``checksum``:
+* ``file_path``
+* ``stable_id``
+* ``decrypted_checksums``, as an array of JSON object with:
 
-  - ``type`` (sha256 only)
+  - ``type``
   - ``value``
 
 .. note:: This allows not to leak out any internal file ID.
 
+An error message arriving in the ``v1.files.errors`` queue contains the following fields:
+
+* ``user``
+* ``file_path``
+* ``reason``
+
 Examples
 --------