holy crap, it actually kinda works now

Previously, I had a stupid system where I would create a thread after
every accept(), and put worker descriptors in a queue. A special
"scheduler" thread would then pick them out, and give out jobs to
complete.

The problem was, of course, I couldn't conveniently poll job status from
workers. I thought about using poll(), but that turned out to be a
horribly complicated API. How do I deal with partial reads, for example?
I don't honestly know.

Then it hit me that I could just use the threads that handle accept()ed
connections as "worker threads", which would synchronously schedule jobs
and wait for them to complete. This solves every problem and removes the
need for a lot of inter-thread synchronization magic. It even works now,
holy crap! You can launch and terminate workers at will, and they will
pick up new jobs automatically.

As a side not, msg_recv_and_handle turned out to be too limiting and
complicated for me, so I got rid of that, and do normal
msg_recv/msg_send calls.

1 files changed, 14 insertions, 4 deletions

diff --git a/src/client.c b/src/client.c
index be46ad1..c711235 100644
--- a/src/client.c
+++ b/src/client.c
@@ -21,12 +21,22 @@ void client_destroy(const struct client *client)
 
 int client_main(const struct client *client, int argc, char *argv[])
 {
-	int result, ret = 0;
-	struct msg msg = {argc, argv};
+	struct msg request = {argc, argv};
+	struct msg response;
+	int ret = 0;
 
-	ret = msg_send_and_wait(client->fd, &msg, &result);
+	ret = msg_send_and_wait(client->fd, &request, &response);
 	if (ret < 0)
 		return ret;
 
-	return result;
+	if (msg_is_error(&response)) {
+		print_error("Server failed to process the request\n");
+		ret = -1;
+		goto free_response;
+	}
+
+free_response:
+	msg_free(&response);
+
+	return ret;
 }