summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorPiotr Szarmanski2022-10-24 10:50:11 +0200
committerPiotr Szarmanski2022-10-24 10:50:11 +0200
commitc4b44fb12108c0764d1fa4ef1c37f11a54379343 (patch)
treeb5bb4d586e7973537608b73a7def903667c33f42 /README
parent087b4ea280caa05e7213eb2b051782086c96efba (diff)
Add hash-backend and update README.
Diffstat (limited to 'README')
-rw-r--r--README17
1 files changed, 17 insertions, 0 deletions
diff --git a/README b/README
index 21afb2f..606afba 100644
--- a/README
+++ b/README
@@ -41,3 +41,20 @@ function will attempt to decode an ERIS read-capability in parallel into a file
specified by the OUTPUT-FILE string or pathspec.
See the docstrings of the specific functions for more details.
+
+
+
+A high-level API is provided for convenience in backend.lisp. The concept is
+that a backend object is created, which holds information like output-function,
+fetch-function, caching details, block-size, etc. and the {en/de}coding
+functions simply take the backend as an argument.
+
+This interface consists of two generic functions: store-data, for encoding data,
+and fetch-read-capability, for retrieving the contents of a read-capability
+object.
+
+As an example, a file-based backend called file-backend is provided. It can be
+used simply by making an instance of the 'file-backend class with a :directory
+argument, which will point to the directory in which ERIS data is to be stored.
+
+There is also hash-backend, which implements a simple hash-table backend.