aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/src/msg.c (follow)
Commit message (Collapse)AuthorAge
* sanitize #include-sEgor Tensin2023-06-13
|
* msg: rework some APIsEgor Tensin2023-06-11
|
* msg: add msg_send_from_argv shortcutEgor Tensin2023-06-09
|
* add {file,net}_close as a wrapper to close(2)Egor Tensin2023-06-09
|
* msg: strings, not wordsEgor Tensin2023-05-15
|
* msg: add functions for one-off communicationEgor Tensin2023-05-14
|
* msg: enforce at least one wordEgor Tensin2023-05-14
| | | | Also, move some stuff to net.c where it belongs.
* best practices & coding style fixesEgor Tensin2023-05-13
| | | | | | | | * I don't really need to declare all variables at the top of the function anymore. * Default-initialize variables more. * Don't set the output parameter until the object is completely constructed.
* add command module to handle request-response communicationsEgor Tensin2023-05-13
|
* make struct ci_queue_entry opaqueEgor Tensin2023-04-29
|
* net: add struct bufEgor Tensin2023-04-29
|
* add copyright noticesEgor Tensin2022-12-02
|
* log: refactoringEgor Tensin2022-09-08
|
* net: more portableEgor Tensin2022-08-30
| | | | Use a predefined byte order, integers with fixed width, etc.
* make proper "error" messagesEgor Tensin2022-08-28
| | | | | Previously, the client had no way to distinguish errors from succesful calls.
* msg: fix a buffer overflowEgor Tensin2022-08-28
| | | | Thanks, Valgrind!
* holy crap, it actually kinda works nowEgor Tensin2022-08-28
| | | | | | | | | | | | | | | | | | | | | | | 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.
* msg: add msg_copy, refactoringEgor Tensin2022-08-25
|
* msg: refactoringEgor Tensin2022-08-25
|
* net: rework APIEgor Tensin2022-08-25
| | | | | | | | | | First, rename all API functions so that they start with net_. Second, abstract the basic TCP server functionality into tcp_server.c. This includes reworking net_accept so that it's a simple blocking operation, and putting the callback stuff to tcp_server.c. Also, the server now uses detached threads instead of fork(), since I want connection handlers to share memory.
* msg: add msg_dump_unknownEgor Tensin2022-08-25
|
* cmd -> msgEgor Tensin2022-08-23
This I feel better conveys the meaning.