expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2026-03-05 14:46:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

wsgi - online edit of handbook/troggle/trogspeculate.html

Browse Source
This commit is contained in:
Philip Sargent
2026-02-15 00:20:10 +00:00
committed by Expo on server
parent 4f3c1be838
commit 4cb3323ea0
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
handbook/troggle/trogspeculate.html
View File

@@ -130,7 +130,7 @@ could mean that we could gain.
<p>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 href="#mud">a much bigger job</a><sup>*</sup> than you might think).
would need to create all our own indexing and cross-referencing code (which is <a href="#mud">a much bigger job</a><sup>*</sup> 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).
<p>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