]> source.dussan.org Git - rspamd.git/commit
projects / rspamd.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: f03f0a8) | patch
[Rework] Serialize control commands
authorVsevolod Stakhov <vsevolod@rspamd.com>
Mon, 22 Apr 2024 14:49:47 +0000 (15:49 +0100)
committerVsevolod Stakhov <vsevolod@rspamd.com>
Mon, 22 Apr 2024 14:49:47 +0000 (15:49 +0100)
commit6d1762d85e00e6d3b0f8084f37c4c45cfdea1e1b
treeed40e412673bf3c5b45702fbc5a6b7bb56426ccftree | snapshot
parentf03f0a88cf34bb63c45446c5bae92475b92f81ffcommit | diff
[Rework] Serialize control commands

In fact, we cannot send multiple commands and read them through the pipe. It has
caused multiple weird issues in the past but I can now see clearly how it should
be done. We should send commands and serialize all requests pending to let them
being sent one by one, after reply for the previous command has been received.
src/libserver/rspamd_control.c diff | blob | history
src/libutil/libev_helper.c diff | blob | history
Rapid spam filtering system: https://github.com/rspamd/rspamd