aboutsummaryrefslogtreecommitdiff
path: root/client/libacron/README.md
diff options
context:
space:
mode:
authorTrumeet <yuuta@yuuta.moe>2022-07-23 11:32:53 -0700
committerTrumeet <yuuta@yuuta.moe>2022-07-23 11:32:53 -0700
commit34c53bc3d396934df94431f7b76972180b1b0a8c (patch)
tree4fc0a2ad83c9c2217772b13725f29cf6f56a0824 /client/libacron/README.md
parent6c49e2e93b23defd51d4b342baad5a9c3f843ea1 (diff)
downloadacron-34c53bc3d396934df94431f7b76972180b1b0a8c.tar
acron-34c53bc3d396934df94431f7b76972180b1b0a8c.tar.gz
acron-34c53bc3d396934df94431f7b76972180b1b0a8c.tar.bz2
acron-34c53bc3d396934df94431f7b76972180b1b0a8c.zip
feat(acronc): guard the connection using a mutex
Signed-off-by: Trumeet <yuuta@yuuta.moe>
Diffstat (limited to 'client/libacron/README.md')
-rw-r--r--client/libacron/README.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/client/libacron/README.md b/client/libacron/README.md
index 09e36dc..d52a4c3 100644
--- a/client/libacron/README.md
+++ b/client/libacron/README.md
@@ -261,6 +261,9 @@ it is the caller's responsibility to guard the whole connection with a mutex. li
provide that because this may limit the flexibility. After locking, it is safe to call the
connection-related functions from any threads.
+Example `acronc/main.c` has a naive cross-platform example of how to guard the connection using
+a mutex.
+
## Roadmap
* Make unit tests