From 4cb3323ea099b3563dc22bb83ab5110b16d34f07 Mon Sep 17 00:00:00 2001 From: Philip Sargent Date: Sun, 15 Feb 2026 00:20:10 +0000 Subject: [PATCH] wsgi - online edit of handbook/troggle/trogspeculate.html --- handbook/troggle/trogspeculate.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/handbook/troggle/trogspeculate.html b/handbook/troggle/trogspeculate.html index a10696a95..30fa2e14d 100644 --- a/handbook/troggle/trogspeculate.html +++ b/handbook/troggle/trogspeculate.html @@ -130,7 +130,7 @@ could mean that we could gain.

Writing our own multi-user code would not be sensible, hence the database. But we could move to a read-only system where the only writing happens on data-import. Then we could use python 'pickle()' or 'json()' read-only data structures, but we -would need to create all our own indexing and cross-referencing code (which is a much bigger job* than you might think). + would need to create all our own indexing and cross-referencing code (which is a much bigger job* than you might think - in fact, it is impossible in a standard wsgi/asgi architecture where there is no shared memory between users and each session is independent).

There would be more lower-level code, but the different segments of the system could be in caving-sensible modules not django-meaningful modules. And we would not have all the extra