out of curiosity, why is mupdate multi-threaded in the first place?
I asked around last week but it seems like that answer has been lost to
history. It was added a long time ago, so it might have been a "threads
are cheaper than processes" decision. The initial commit for
imap/mupdate.c (2001) describes it as "added mupdate for possible
lightweight acap replacement", but I don't know what "acap" was!
I know that, because I still use one of the very few clients that support
ACAP, and I used to run my own ACAP server so I could use it:
<https://en.wikipedia.org/wiki/Application_Configuration_Access_Protocol>
--
Sebastian Hagedorn - Weyertal 121, Zimmer 2.02
Regionales Rechenzentrum (RRZK)
Universität zu Köln / Cologne University - Tel. +49-221-470-89578
