summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2018-10-31 10:08:42 +0200
committerLars Wirzenius <liw@liw.fi>2018-10-31 10:08:42 +0200
commit4ff8e269133357601ab77de23e6d1ae70633e5bb (patch)
treeb06a632931e66f68fa55e6ce91ebde3b27042f88
parent6e5b3c500267bdb6c18528da0e9235e1feb3a99c (diff)
downloadmuck-poc-4ff8e269133357601ab77de23e6d1ae70633e5bb.tar.gz
Add: why Ick will use Muck
-rw-r--r--README5
1 files changed, 4 insertions, 1 deletions
diff --git a/README b/README
index 2c7a45f..4ae0562 100644
--- a/README
+++ b/README
@@ -38,7 +38,10 @@ liw@liw.fi.
Muck will eventually become part of the ick project
(https://ick.liw.fi/), and when it does, the usual ick communication
-channels will be appropriate.
+channels will be appropriate. Ick will use Muck to add some protection
+against concurrent changes, and to prevent users from seeing each
+others' data. It seems better to do these in Muck than in the Ick
+controller directly.
I hope Muck will come to be useful for others as well. If you think it
might be useful for you, but have reservations or use cases, please