resolver.texi (1041B)
1 @anchor{resolver} 2 @chapter Resolvers 3 4 5 The resolver element describes endpoints that can be used as key-value stores to expand content. 6 7 Content to resolve may include: 8 9 @itemize 10 @item Ledger entries 11 @item 12 @end itemize 13 14 Typically, they are content-addressed stores where a digest is used to retrieve content corresponding to the digest from a @xref{resolver}. 15 16 Resolvers are defined per lookup key algorithm, and any algorithm may have several resolvers defined. Defining more than one resolver per algorithm enables redundancy in conent retrieval. 17 18 19 @section Defining a resolver 20 21 The endpoint is defined as a combination of protocol for retrieval, location for retrieval and algorithms for content lookup key. An example for a @code{sha256} resolver could be defined as: 22 23 @example 24 <resolver algo="sha256" proto="https">foo.com/content/</resolver> 25 @end example 26 27 28 @section Security 29 30 Note that even if an endpoint is trusted, it is always up to the client to verify that any digest used as a lookup key actually matches the content returned.