Paul J Stevens wrote:
Using threading is not a goal in itself, but a means.
One of the goals for 2.3+ is adding new imap capabilities like NOTIFY
that require a lot of IPC between running imapd processes. Using threads
will make that quite straightforward.
OK, though IPC is possible in a multi-process model, but I agree,
communication is probably the one place where a threaded system is more
simple than multi-process.
Another goal is scaling up the number of concurrent connected clients
without depleting the database connections. Using connection pools is a
best practice there, and even though that could be done in a
multi-process architecture, this is generally done using threads.
I don't see how this makes things better, what it sounds like you are
suggesting is that DBMail will become in addition to an IMAP server, a
database connection pooling engine. There are tools out there that do
this already.
So yes, imo also there's a very solid case for threads in dbmail. But
like Aaron says, it will take some time to do this right. Neither I nor
Aaron (afaik) have any experience with threads in C so we'll have to
learn how to do it as we go along :-)
This sounds scary to me. Obviously it's not my project and I'm not the
one coding, I'm just worried as an admin that depends on DBMail that we
are going to open up a large can of worms for dubious gain.
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
