about summary refs log tree commit homepage
path: root/Documentation
diff options
context:
space:
mode:
authorEric Wong <e@80x24.org>2021-04-24 09:28:44 +0000
committerEric Wong <e@80x24.org>2021-04-24 16:10:02 -0400
commit4492b8e066570fd841fff5528100e8197645c85e (patch)
tree69a5b4b61d3155b7997ce54a41b0b98f92b16716 /Documentation
parent15a3ec65a3ad0c1dcd686c2075d3f68730d416de (diff)
downloadpublic-inbox-4492b8e066570fd841fff5528100e8197645c85e.tar.gz
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/lei_design_notes.txt12
1 files changed, 12 insertions, 0 deletions
diff --git a/Documentation/lei_design_notes.txt b/Documentation/lei_design_notes.txt
index a5606c05..f1d2ab6f 100644
--- a/Documentation/lei_design_notes.txt
+++ b/Documentation/lei_design_notes.txt
@@ -18,3 +18,15 @@ SQLite, and Xapian across multiple processes.
 The coupling of IMAP and NNTP network latency to local storage
 is a current weakness of public-inbox-watch.  Therefore, -watch
 will likely adopt the daemon architecture of lei in the future.
+
+Read/write vs read-only storage
+-------------------------------
+
+public-inboxes are intended to be written and read by different
+Unix users.  Commonly, a single Unix user or group will write to
+a public-inbox, but the inbox will be served by a user with
+read-only permissions (e.g. "www-data" or "nobody").
+
+lei/store is intended to be read and written by a single user,
+thus we can rely on the Write-Ahead-Log journal of SQLite to
+improve performance: <https://sqlite.org/wal.html>