Guy Hulbert wrote:
If it were PD, would you have tried to build an XS interface instead ?
Does that even make sense ?
What benefit do you imagine it'd have? Which part of "core qmail-
smtpd" is slow in qpsmtpd-{fork,select}server? Did you look at the
qmail-smtpd code?
No but you did. That's why I'm asking. My "would" above is
subjunctive.
What I'm asking, is *if* the license had already been changed, *would*
you have implemented qpsmtpd via XS rather than rewriting qmail-smtpd
entirely.
I don't think there would be a big win from this. If you run perl at
all the problem is in the memory footprint and the difficulty in keeping
shared pages across forked processes. It might be a win, though, to run
the stock front end for some operations, letting it chat with a perl
process for certain steps. The down side is that multiplexing step-wise
operations to a small number of backend processes means that variables
don't hold values for the entire delivery process.
--
Les Mikesell
[EMAIL PROTECTED]
