From df85b736cea32bd04e4a80042b9b3c67642d57ba Mon Sep 17 00:00:00 2001 From: Trumeet Date: Sat, 23 Jul 2022 13:29:24 -0700 Subject: refactor(acronc): rename acronc to helloworld Signed-off-by: Trumeet --- client/libacron/README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'client/libacron/README.md') diff --git a/client/libacron/README.md b/client/libacron/README.md index d52a4c3..4514e21 100644 --- a/client/libacron/README.md +++ b/client/libacron/README.md @@ -177,8 +177,8 @@ The client also needs to supply its own `on_send` function. libac will call that needs to write anything to the socket. When calling that function, the socket pointer will be passed as-is. -No worries, `acronc/net.c` provides a ready-to-use example of cross-platform (Unix and Windows) blocking -socket client. See `acronc/main.c` for more details. +No worries, `apps/helloworld/net.c` provides a ready-to-use example of cross-platform (Unix and Windows) blocking +socket client. See `apps/helloworld/main.c` for more details. ```c void *connection = NULL; @@ -231,7 +231,7 @@ The program can make requests using `ac_request()`: ```c ac_config_t conf = { - .name = "acronc" + .name = "helloworld" }; ac_request_cmd_t req = { .type = AC_REQUEST_CMD, @@ -252,7 +252,7 @@ The client must manually close its socket after calling `ac_disconnect()`. > on the roadmap. -Read more: `acronc/main.c` example client. +Read more: `apps/helloworld/main.c` example client. #### Connection Threading @@ -261,7 +261,7 @@ 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 +Example `apps/helloworld/main.c` has a naive cross-platform example of how to guard the connection using a mutex. ## Roadmap -- cgit v1.2.3