lsd0004

commit 52754000569383b24e2e7b4644cbaaf2d24b35d9
parent 8c4fc016643b627516be58aa99ca8b9b55d631cf
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Wed, 29 Dec 2021 15:06:57 +0100

put update

Diffstat:
M
draft-schanzen-r5n.xml
 | 
36
+++++++++++++++++++++++++++++-------

1 file changed, 29 insertions(+), 7 deletions(-)
diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
@@ -227,12 +227,12 @@ Connectivity | |Underlay|  |Underlay|
          The GET procedure is defined as follows:
        </t>
          <artwork name="" type="" align="left" alt=""><![CDATA[
-GET(Key[, QueryParams]) -> Results as List
+GET(Key[, GetParams]) -> Results as List
            ]]></artwork>
        <t>
          The procedure takes a single additional <tt>QueryParams</tt>
          argument in order to specify detailed query parameters.
-         The <tt>QueryParams</tt> consist of the following parameters:
+         The <tt>GetParams</tt> consist of the following parameters:
        </t>
        <dl>
          <dt>BlockType</dt>
@@ -260,6 +260,9 @@ GET(Key[, QueryParams]) -> Results as List
            The default setting of this parameter is empty.
          </dd>
        </dl>
+       <t>
+         The <tt>RouteOptions</tt> consist of the following flags:
+       </t>
        <dl anchor="route_options">
          <dt>DemultiplexEverywhere</dt>
          <dd>
@@ -290,15 +293,34 @@ GET(Key[, QueryParams]) -> Results as List
          The PUT procedure is defined as follows:
        </t>
          <artwork name="" type="" align="left" alt=""><![CDATA[
-PUT(Key, Type, Block[, RouteOptions])
+PUT(Key, Block, BlockType[, PutParams])
          ]]></artwork>
        <t>
-         The procedure takes two mandatory arguments.
+         The procedure takes three mandatory arguments.
          The first argument is the query
-         key under which the Block is to be stored.
-         The PUT procedure may also allow the caller
-         to specifiy put options.
+         key under which the block is to be stored.
+         The second parameter is the block payload.
+         The third parameter is the type of the block payload.
+         Block types are defined in <xref target="block_types"/>.
+         The PUT procedure also allows an optional <tt>PutParams</tt>
+         parameter.
        </t>
+       <dl>
+         <dt>ReplicationLevel</dt>
+         <dd>The default setting of this parameter is X (FIXME).</dd>
+         <dt>RouteOptions</dt>
+         <dd>
+           are used in order to indicate certain
+           processing requirements for messages.
+           Any combination of options as defined in <xref target="route_options"/>
+           may be specificied.
+           The default setting of this parameter is that no option is set.
+         </dd>
+         <dt>Expiration</dt>
+         <dd>
+           is the requested expiration date for the block payload.
+         </dd>
+       </dl>
      </section>
    </section>
    <section anchor="underlay" numbered="true" toc="default">