commit e9e07b0449f9ad9ece320830ef546df52e05dbe8
parent 898087a43b3ddb5de9bc3d26aabdb3714563b185
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Sat, 25 Dec 2021 13:03:29 +0100
add block evaluations
Diffstat:
1 file changed, 24 insertions(+), 0 deletions(-)
diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
@@ -261,6 +261,30 @@ PUT(key[, options], BLOCK)
<section anchor="blockstorage" numbered="true" toc="default">
<name>Block Storage</name>
<section>
+ <name>Block Processing</name>
+ <dl>
+ <dt>OK_MORE</dt>
+ <dd>Valid result, and there may be more.</dd>
+ <dt>OK_LAST</dt>
+ <dd>Last possible valid result.</dd>
+ <dt>OK_DUPLICATE</dt>
+ <dd>Valid result, but duplicate.</dd>
+ <dt>RESULT_INVALID</dt>
+ <dd>Invalid result. Block does not match query. Value = 4.</dd>
+ <dt>RESULT_IRRELEVANT</dt>
+ <dd>Block does not match xquery. Valid result, but not relevant for the request.</dd>
+ <dt>REQUEST_VALID</dt>
+ <dd>Query is valid, no reply given.</dd>
+ <dt>REQUEST_INVALID</dt>
+ <dd>
+ Query format does not match block type. For example, xquery not
+ given or xquery_size not appropriate for type.
+ </dd>
+ <dt>TYPE_NOT_SUPPORTED</dt>
+ <dd>Specified block type not supported by this implementation. FIXME: We may not need this for the spec.</dd>
+ </dl>
+ </section>
+ <section>
<name>Block Types</name>
<t>
Applications can and should define their own block types.